The Charter Phase
The Charter phase transforms a feature idea into a structured charter. Run /auro.charter "your feature description" and Auro creates a branch, generates a charter from the template, and marks ambiguities.
What Gets Generated
Section titled “What Gets Generated”Input
Feature Idea
Command
/auro.charter
Output
Branch Created
Artifact
charter.md Generated
Review
Clarify Ambiguities
The charter contains four sections:
- User Stories — Prioritized P1/P2/P3 scenarios with acceptance criteria
- Functional Requirements — Numbered FR-001+ requirements with entity definitions
- Success Criteria — Measurable outcomes SC-001+ in Given/When/Then format
- Edge Cases — Boundary conditions and error scenarios
Each user story must be independently testable. If you implement only one story, you should still have a viable MVP.
Key Principle
Section titled “Key Principle”Ambiguity is marked, not assumed. When the agent encounters something unclear, it writes [NEEDS CLARIFICATION: question] instead of guessing. You resolve these with /auro.clarify.
Pages in This Section
Section titled “Pages in This Section”- User Stories — P1/P2/P3 priority system
- Requirements — FR numbering and entity modeling
- Success Criteria — Measurable outcomes
- Clarify Ambiguities — Resolving unknowns interactively