writing-plans

To break down a React Native spec, convert it into a multi-step implementation plan that includes file mappings, TDD steps, and commit checkpoints for each subsystem. This ensures every agentic task is self-contained and actionable before coding begins.

An agentic workflow implementation plan should include a structured header, goal summary, architecture note, tech stack, scope assessment, exact file mappings, commit-friendly task sequences, and RED-GREEN testing steps to ensure compliant execution.

You enforce TDD steps and commit checkpoints by laying out bite-sized, commit-friendly task sequences with RED-GREEN testing phases. The plan must document your testing preference and enforce a final self-review checklist covering spec coverage and type consistency.

Yes, task decomposition allows you to split complex React Native subsystems into standalone plans. A scope assessment ensures each subsystem gets its own plan with exact file mappings, placeholder-free task steps, and a confirmed testing strategy.

The best way to document a testing strategy is to ask the user for their TDD preference upfront, record whether tests will be written, and enforce a final self-review checklist that verifies spec coverage, placeholder absence, and type consistency.