workflow-plan

Generate vertically-sliced commit plans with testing strategies from requirements.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed, vertically-sliced commit plans for software development tasks, ensuring each commit is independently deployable and contributes meaningful value.

Core Features & Use Cases

  • Task Decomposition: Breaks down complex tasks into manageable, commit-sized chunks.
  • Vertical Slicing Enforcement: Guarantees that each commit delivers a complete, testable piece of functionality, preventing horizontal slicing anti-patterns.
  • Test Strategy Guidance: Specifies appropriate testing methodologies (TDD, TEST-AFTER, NO-TEST) and levels (UNIT, INT, COMP, E2E) for each commit.
  • Use Case: After analyzing a feature requirement, use this Skill to generate a step-by-step commit plan for the development team, outlining the exact tasks, testing strategy, and verification methods for each commit.

Quick Start

Use the workflow-plan skill to generate an implementation plan for the task 'Implement User Authentication' with a limit of 5 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 commit-level implementation plan for software development tasks?

To generate a commit-level implementation plan, provide your feature requirements to the workflow-plan automation tool. It parses your input and outputs a structured, vertically-sliced commit strategy in Korean documentation.

What is vertical slicing in software development and how does it apply to commits?

Vertical slicing breaks down complex tasks into commit-sized chunks where each commit delivers complete, independently deployable functionality. This approach prevents horizontal slicing anti-patterns by ensuring every commit contributes meaningful value.

How do I enforce independent deployability when planning a software development workflow?

You enforce independent deployability by structuring your development workflow with vertically-sliced commits. The plan generation guarantees each commit is a complete, testable piece of functionality that can be deployed independently.

What testing strategies should I apply per commit when doing TDD workflow automation?

Per-commit testing strategies include TDD, TEST-AFTER, or NO-TEST methodologies across UNIT, INT, COMP, and E2E levels. The plan generation specifies the appropriate testing methodology and verification methods for each commit.

Can I limit the number of commits when generating a vertically-sliced task decomposition plan?

Yes, you can limit the number of commits in your task decomposition plan. When initiating the workflow generation, specify the maximum commit count, such as a limit of 5 commits, to constrain the output structure.

Do I need prior analysis to use a commit strategy generator for my feature requirements?

Prior analysis is not strictly required to generate a commit strategy. The tool can parse user-provided requirements directly, though integrating prior analysis input will yield a more detailed, vertically-sliced commit plan.