feature-grill

To create an executable implementation plan, you must clarify feature scope, resolve context, and make domain decisions. This process bridges high-level requests and actionable tasks by generating a detailed plan with validation steps.

The best way to document architectural decisions during domain modeling is to record terms, assumptions, and context directly in a CONTEXT.md file, ensuring alignment and maintaining contextual documentation alongside the implementation plan.

Feature clarification works by deep diving into a feature to understand its complexity, interactions, and edge cases. It requires user input on scope and decision-making to ensure the resulting implementation plan is well-defined.

Yes, user input is required to generate a detailed implementation plan. You must provide information on feature scope, decision-making, and context resolution to ensure the plan is actionable and aligned with project goals.

Yes, you can use this approach to align team understanding before development. It grills features to produce a well-defined, implementation-ready plan and updates contextual documentation to ensure clarity across the team.

A limitation of generating implementation plans is that the Skill requires active user participation for context resolution and decision-making. It cannot autonomously define scope or make architectural decisions without direct user input.