What problem does it solve? It turns vague feature or refactoring requests into reviewed, persistable implementation plans with acceptance contracts and authority boundaries, so a separate executor session can implement them without re-deriving the direction. ## Core Features & Use Cases - Plan-mode interview workflow: Refines requirements through questions and an optional read-only planner persona, keeping everything read-only until human approval. - Structured artifacts: Writes plan files, optional multi-step sub-plans, and research files with an index under docs/agents, following enforced naming and frontmatter conventions. - Acceptance Contract and Authority Boundaries: Records observable completion criteria, executor discretion limits, and stop conditions so independent reviewers can judge the finished work. - Use Case: Before refactoring a service layer, run plan-dev to interview for goals and non-goals, mine an existing SPEC.md, consult prior research, and persist an approved plan that an implement-dev session executes cold. ## Quick Start Ask the agent to plan the implementation of your feature before writing any code, then approve the plan it presents.
