-
Follow the workflow strictly
- Each phase must be completed and confirmed by user before proceeding to next phase
- Never skip phases or proceed without user confirmation
- Use tool when clarification is needed
-
Apply EARS requirement syntax
- Use EARS (Easy Approach to Requirements Syntax) for requirement descriptions
- Format:
While <optional precondition>, when <optional trigger>, the <system name> shall <system response>
-
Reference UI design rules when needed
- If requirements involve frontend pages, must strictly reference
- Determine design style and color palette in requirements phase
- Confirm design details with user before finalizing requirements
-
Update task status
- Keep task status updated in file
- Mark tasks as completed when finished
- Work independently and efficiently while maintaining quality
-
If you determine that the user's input is a new requirement, you can work independently following standard software engineering practices. Confirm with user when necessary, and can use
tool to collect information.
-
Whenever the user inputs a new requirement, to standardize requirement quality and acceptance criteria, you must first understand the problem and requirements clearly. You must confirm with the user before proceeding to the next phase.
First complete the requirements design using EARS (Easy Approach to Requirements Syntax) method. If you determine the requirements involve frontend pages,
you must strictly reference rule file. Determine design style and color palette in the requirements phase. You must confirm requirement details with the user. After final confirmation, the requirements are finalized, then proceed to the next phase.
Save to
specs/spec_name/requirements.md
. After confirming with the user, proceed to the next phase.
After completing the requirements design, based on the current technical architecture and the confirmed requirements above, design the technical solution. It should be concise but accurately describe the technical architecture (e.g., architecture, tech stack, technology selection, database/interface design, test strategy, security). Use mermaid diagrams when necessary.
Save to
specs/spec_name/design.md
. You must confirm with the user clearly, then proceed to the next phase.
After completing the technical solution design, based on the requirements document and technical solution, break down specific tasks. You must confirm with the user clearly, then save to
. After confirming with the user, proceed to the next phase and begin formal task execution. You need to update task status in a timely manner. When executing, work as independently and autonomously as possible to ensure efficiency and quality.