task-plan

Creates implementation plans with PR splitting and edge-case coverage for work tasks.

3|1|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/isizono/calm --skill task-plan-isizono
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: task-plan
Source: https://github.com/isizono/calm/tree/main/.claude/skills/task-plan
Command: npx skills add https://github.com/isizono/calm --skill task-plan-isizono

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When asked to implement a work task, jumping straight into code without a plan leads to oversized PRs, missed edge cases, and lost specification context. This Skill structures the planning phase: it classifies changes into five PR-splitting types, derives expected behaviors from recorded decisions, and produces a plan.md (plus sub-plans) that must be user-approved before any implementation begins. ## Core Features & Use Cases - PR Splitting by 5 Types: Classifies changes into mechanical replacement, schema/data change, new module, behavior change, or removal, and splits work into reviewable PRs with branch strategy and dependencies. - Specification Derivation from cc-memory: Pulls decisions and precedents from the cc-memory database to derive assertable edge cases with explicit derivation memos linking business requirements to expected behavior. - Derivation Verification Sub-Agent: Launches a background verification agent that checks each planned behavior against decision text via verbatim quotation before user confirmation. - Use Case: A user asks to implement a [作業] task tracked in cc-memory. The Skill confirms scope with the user, produces plan.md with a PR table, GO-judgment predictions, and an edge-case coverage table, then waits for approval without writing any code. ## Quick Start Ask the AI to create an implementation plan for a work task that has no plan.md yet, and it will classify the changes, draft plan.md with sub-plans, and present it for your confirmation.

Frequently Asked Questions about task-plan

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

FAQPage Schema
How do I split a large implementation task into multiple PRs?▼

Classify each change into one of five types: mechanical replacement, schema/data change, new module, behavior change, or removal. Group only changes with the same review style into one PR, and record branch names, base branches, and dependencies in a PR-splitting table.

How to plan a coding task before implementation with an AI agent?▼

Confirm the specification scope with recorded decisions first, then generate a plan.md containing a TODO list, implementation order, edge-case coverage table, and acceptance criteria. Wait for explicit user approval before writing any code.

When should I use a stacked PR strategy versus an integration branch?▼

Use stacked PRs targeting main directly when each PR is independently safe to merge. Use an integration branch when intermediate states would break main or when partial merges have no standalone meaning, adding a final merge row to the plan.

What happens if business requirements are missing from the decision records?▼

If behavior-changing implementation lacks a supporting business requirement in cc-memory, the planning is treated as a specification gap. The process pauses so requirements can be confirmed and recorded as decisions before continuing.

Does this planning workflow write any code automatically?▼

No. The Skill's responsibility ends at creating plan.md and sub-plans. It explicitly never proceeds to implementation and waits for user confirmation, with execution handled by a separate task-execute step.