irwebtools developer-handoff
When to use
Use when the task matches: developer-handoff, DEV_READY, handoff.
Purpose
Give developers intent, structure, limitations, and next production steps.
Inputs
- Validated definition and UX
- POC and verification evidence
- Architecture decision
Process
- Summarize product intent in Product language.
- Document FSD structure, changed files, and run setup.
- List known limitations and owners for deferred work.
- Do not grant production release permission.
Outputs
- Product intent
- Implemented features
- FSD structure
- Changed files
- Known limitations
- Production next steps
Verification
- Confirm each output exists and is reviewable.
- Keep Product validation and engineering verification distinct.
- Do not claim completion without evidence.
Restrictions
- Do not rewrite the app during handoff.
- Do not omit mocks as if they were real integrations.
- Do not treat DEV_READY as production authorization.