workflow-plan

Generate vertically sliced commit plans from workflow analysis into dual-language markdown files.

1|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/specvital/infra --skill workflow-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-plan
Source: https://github.com/specvital/infra/tree/main/.claude/skills/workflow-plan
Command: npx skills add https://github.com/specvital/infra --skill workflow-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams systematically convert workflow analyses into actionable, vertically sliced commit plans.

Core Features & Use Cases

  • Parse user input to extract task name and requirements.
  • Check for an existing docs/work/WORK-{name}/analysis.md and use it to guide plan generation.
  • Decompose work into vertically sliced commits (setup, core, integration, polish) with independent deployability and verification.
  • Generate dual-language plan files: docs/work/WORK-{name}/plan.ko.md and plan.md for agent consumption.

Quick Start

Invoke the workflow-plan skill after running workflow-analysis to generate a concrete, vertically sliced commit plan. Example:

  • /workflow-plan API-REDESIGN limit to 3 commits

Frequently Asked Questions about workflow-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a vertically sliced commit plan from workflow analysis?

To generate a vertically sliced commit plan from workflow analysis, invoke the workflow-plan skill after completing your analysis. It decomposes engineering tasks into independent, deployable commits with explicit verification steps and boundaries.

What is vertical slicing in software engineering commit plans?

Vertical slicing in software engineering commit plans decomposes work into setup, core, integration, and polish commits. This technique ensures each commit is independently deployable and includes explicit verification steps and boundaries.

How do I limit the number of commits in an implementation plan?

To limit the number of commits in an implementation plan, pass the limit parameter when invoking the skill, such as specifying a maximum of 3 commits. This constrains the generated plan to your desired scope.

Does workflow-plan require an existing analysis.md file to generate a plan?

workflow-plan does not strictly require an existing analysis.md file, but it checks for docs/work/WORK-{name}/analysis.md to guide plan generation. Parsing user input allows it to generate plans independently if the file is absent.

Can I generate dual-language implementation plans for agent consumption?

Yes, you can generate dual-language implementation plans for agent consumption. The skill outputs plan.md and plan.ko.md files in the docs/work/WORK-{name}/ directory to support English and Korean.

What types of software engineering tasks are suitable for vertical slicing commit plans?

Vertical slicing commit plans are suitable for software engineering tasks such as API redesigns, refactors, or feature migrations. These tasks benefit from decomposition into independent, deployable commits with explicit verification steps.