workflow-plan

Generates commit-level implementation plans with vertical slicing and test classification from task requirements.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/kubrickcode/cine-mirror --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/cine-mirror/tree/main/.agents/skills/workflow-plan
Command: npx skills add https://github.com/kubrickcode/cine-mirror --skill workflow-plan-kubrickcode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature analysis into an actionable implementation plan is error-prone: commits often get sliced horizontally (types, then logic, then tests), leaving each commit undeployable and untestable on its own. This Skill produces a structured, commit-level plan where every commit is independently deployable and carries an explicit test strategy. ## Core Features & Use Cases - Vertical Commit Slicing: Decomposes work into commits that each include types, logic, and tests, ordered Setup → Core → Integration → Polish. - Test Classification: Assigns each commit a test requirement (TDD, TEST-AFTER, NO-TEST) and test level (UNIT, INT, COMP, E2E) with justification rules for expensive E2E tests. - Analysis Integration: Reads the selected approach from a prior analysis.md when available, or interprets direct user input as requirements. - Use Case: After analyzing a refactoring task, run the plan step to produce a Korean-language plan.md with a checklist per commit, verification methods, and a principle-violation justification table. ## Quick Start Run /workflow-plan REFACTORING limit to 3 commits to generate a vertically sliced implementation plan at docs/work/REFACTORING/plan.md.

Frequently Asked Questions about workflow-plan

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

FAQPage Schema
How do I create an implementation plan with commit-level tasks?▼

Run /workflow-plan followed by a task name and optional constraints, such as a commit count limit. The Skill reads the prior analysis.md if it exists, then writes a plan.md with a checklist, test requirement, and verification method for each commit.

What is vertical slicing in commit planning?▼

Vertical slicing means each commit contains types, logic, and tests together so it is independently deployable and testable. Horizontal slicing, where types, logic, tests, and UI are split into separate commits, is explicitly forbidden because each commit would be functionally incomplete.

When should a commit use TDD versus TEST-AFTER?▼

TDD applies to business logic with conditionals, calculations, validations, and state mutations, where the failing test is written first. TEST-AFTER applies to UI components and external API or database integrations, while config files, docs, and pure types are NO-TEST.

When are E2E tests justified in a plan?▼

E2E tests are justified only when the flow cannot be tested at a lower level, is revenue or trust critical, has broken in production before, and failure would be catastrophic. Scenarios adequately covered by UNIT and INT tests should not use E2E.

Does workflow-plan require a prior analysis document?▼

No. If docs/work/{task-name}/analysis.md exists, the plan extracts the selected approach and completion criteria from it. If not, the Skill interprets the user input directly as the requirements source and proceeds.