Add Greenfield Application Development workshop and module

[devin-ai-integration]

Summary

Adds a new Greenfield Application Development workshop — the first workshop where Devin builds an entire application from scratch with no starting codebase. Specs are embedded directly in the module file (no separate repo needed).

New files:

• modules/application-development/greenfield-application-development.md — module with embedded Operations Dashboard CRUD spec (data model, API contract, UI requirements) and 2-step instructions (Paste into Devin → Review & Give Feedback)
• workshops/greenfield-application-development/README.md — 4-lab workshop: Requirements → Build → Test → Extend, with duration variants (1–3 hours)

Updated indices:

• README.md — directory tree, module count 77→78, Application Development 7→8
• modules/README.md — module table, composition suggestions
• modules/application-development/README.md — module table, category description
• workshops/README.md — workshop table

Updates since last revision

• Removed "Ask Devin" and "Read the DeepWiki" steps from both the module and all 4 workshop labs. Since there is no pre-existing remote repo, these steps don't apply. All labs now use a simplified 2-step format: Step 1 (Paste into Devin) → Step 2 (Review & Give Feedback). This deviates from the standard 4-step module pattern used elsewhere — intentional given the no-repo nature of this workshop.

Review & Testing Checklist for Human

• Try the Lab 2 prompt in a real Devin session. This is the core hands-on experience — paste the Step 1 prompt and verify Devin produces a reasonable full-stack app. The prompt quality directly determines workshop quality. None of these prompts have been live-tested yet.
• Verify the "Operations Dashboard" domain framing works for your audience. The original UC1 was "Inventory Management Dashboard" — this was generalized. Confirm the entity name ("Item"), fields, and status rules are the right abstraction or if you'd prefer a different domain.
• Check that Labs 3 & 4 work in a greenfield context. They reference existing modules (TDD, New Feature Development) that normally use pre-existing repos like app_timesheet. The workshop says "adapted" — confirm the prompts make sense when applied to whatever Devin just built in Lab 2.
• Confirm the 2-step format is acceptable. Every other module in the repo uses 4 steps (Paste → Ask Devin → DeepWiki → Review). This module and workshop intentionally skip steps 2 and 3 since there's no remote repo. Verify this inconsistency is fine or if placeholder guidance should be added.
• Verify relative links render correctly on GitHub. Workshop README uses ../../modules/application-development/... paths to link to modules.

Notes

• This is the first module with no repo dependency — a novel pattern in the workshop-metadata system. The "Repositories" section explicitly states this.
• The Step 1 prompt in the module file and Lab 2 of the workshop are intentionally identical (module is the reusable atom, workshop composes it).
• No overlap with the existing legacy-modernization workshop (that covers COBOL/Oracle Forms → Java modernization; this covers building new apps from specs).

Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/685606b2f4e843a0b73e7bd09390b2b0
Requested by: @bsmitches

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.