ce:plan

To turn feature requirements into an implementation plan, you translate feature descriptions into a structured, implementation-ready plan anchored in repository standards. This ensures the output references repo-relative paths and includes explicit test scenarios.

Structuring a technical plan using repository patterns involves mapping requirements to repo-relative paths and defining implementation units. This approach grounds the plan in existing code standards rather than generic architectures.

Use a planning skill when requirements are at least roughly defined and you need structured implementation units. For exploratory or ambiguous requests where requirements are unclear, prefer brainstorming first to establish the scope.

Deepening an implementation plan involves an interactive review of sub-agent findings to add risk analysis and test scenarios. This process enriches the initial plan by validating repository patterns and refining implementation units.

Yes, creating test scenarios from feature descriptions is part of generating an implementation-ready plan. The planning process explicitly includes defining test scenarios alongside mapping implementation units to repository paths.

Implementation planning is designed to anchor outputs in repository standards and patterns. While it can process minimal inputs, the resulting plan relies heavily on referencing repo-relative paths to be effective.