Feature Dev

This is the methodical approach to feature work: it forces you to explore the codebase first, ask clarifying questions before writing any code, compare architectural approaches, then implement with testing baked in. The structure is opinionated about sequence (discovery, exploration, questions, design, implementation, testing, review) and leans heavily on parallel agents for code exploration, architecture design, and review. It's built for when you're adding something substantial to an unfamiliar codebase and want guardrails against the usual mistakes like assuming requirements or skipping edge cases. The clarifying questions phase is explicitly non-skippable, which will either save you or annoy you depending on how well-specified your features usually are.