writing-plans

To create an implementation plan from software requirements, this Skill analyzes your project context, architecture, and CI signals to produce an executable plan with vertical slices, dependency graphs, and validation commands.

Vertical slice planning breaks down multi-step software changes into small, independently verifiable tasks instead of broad implementation phases, ensuring each slice has clear scope, affected files, and exact validation commands.

Mapping dependencies and validation steps for a refactoring task involves identifying blocked-by relationships and specifying exact commands to verify progress, which this Skill automates by inspecting your repository architecture and tests.

Yes, you can generate a file-level scope and test scenarios for bug fixes by providing the understood requirements and project context, allowing the Skill to align the actionable plan with your existing workflows and tests.

Yes, the planning approach works with your existing CI signals and repository conventions by directly inspecting them to shape a realistic, project-aligned execution guidance for feature changes and refactors.

You should avoid automated implementation plan generation for simple, single-file modifications that do not require multi-step software changes, dependency graphs, or complex vertical slice architecture to verify progress.