Use AI-assisted software planning with review
AI can help organize an idea, but someone still needs to check the requirements and decisions. CSR keeps the plan and its evidence available for that review.
Describe outcomes before tools
Explain the users, their current problem, and the task they need to complete. Add constraints you already know, including privacy, accessibility, budget, and deployment needs. Avoid choosing a technology merely because it appears in a generated suggestion.
Review each stage
The guided Create workflow proceeds through Describe, Research, Components, Architecture, Delivery and Release, AI Coding Tool, and Export. Each stage has contextual explanations, saved choices, and Back and Continue controls. Review generated requirements against the original problem and correct omissions before using them as development instructions.
Keep evidence distinct from suggestions
A proposed component, architecture, or estimate is not a demonstrated result. Review source references and record unresolved assumptions. Provider availability and configured authorization affect which research operations are available. Planning does not grant permission to run unrestricted paid AI calls or publish private materials.
Handoff deliberately
Choose the coding tool and environment you intend to use, then export the plan as Markdown, a CSR ZIP, or the supported Spec Kit handoff. The export carries planning inputs; it does not establish that code is complete, tested, or ready for production. Keep implementation and release acceptance criteria with the work.