react-writing-plans

To convert a React feature spec into an implementation plan, provide the spec to generate a structured, executable task breakdown. The plan aligns with architecture contracts and guides development for multi-file frontend features.

The best way to break down multi-file React features is generating a task-level blueprint using Create, Modify, and Test formats. This provides precise file paths and behavior notes for components, stores, or API integrations.

Architecture contract referencing ensures generated React plans satisfy existing architectural rules by explicitly referencing the architecture doc. This aligns the task breakdown and formatting with established project constraints.

Generated React implementation plans are saved to the _docs/plans directory. They are stored as dated markdown files, formatted as _docs/plans/<date>-<feature>.md, ensuring easy reference and team handoff.

Yes, you can use this for frontend features requiring API integrations and stores. It applies to multi-file React features, producing a structured implementation plan that details tasks for these specific integrations.

You do not strictly need a PRD, but you need a feature spec or requirements document. The skill transforms specs or PRDs into an actionable, structured task breakdown aligned with your architecture contracts.