원클릭으로
sdlc-plan
Break specs into ordered tasks with acceptance criteria. Use after sdlc-spec to create executable task breakdown.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Break specs into ordered tasks with acceptance criteria. Use after sdlc-spec to create executable task breakdown.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Execute tasks with pre/post drift checks and verification gates. Use after sdlc-plan to implement with accuracy guarantees.
Configure SDLC model tiers. Interactive TUI via /sdlc-choose, quick switch via /sdlc-tier.
Final verification against spec with full evidence chain. Use after sdlc-execute to confirm feature is complete.
Create feature specs through collaborative brainstorming. Use when starting new features, writing requirements, or defining acceptance criteria.
| name | sdlc-plan |
| description | Break specs into ordered tasks with acceptance criteria. Use after sdlc-spec to create executable task breakdown. |
Model auto-switch: Extension switches to plan-tier model automatically.
Rules: Assign task types so executor loads correct rules from
docs/rules/.Previous:
/skill:sdlc-spec| Next:/skill:sdlc-execute
Transform spec into ordered tasks with testable criteria, dependencies, and scope estimates.
Dependency: Requires pi-memctx.
plan_tracker_ide:
action: check_approval
phase: plan
If APPROVED, skip to tracker status and handoff. Do not re-ask for plan confirmation.
memctx_search:
query: "spec {feature}"
mode: keyword
Or read from docs/specs/{path}/spec.md.
For each task, create docs/specs/{feature}/tasks/NN-{name}.md:
# Task NN: {Name}
**Scope:** S | M | L
**Type:** backend | frontend | mixed
**Dependencies:** [Task numbers]
## Description
[What this accomplishes]
## Acceptance Criteria
- [ ] [Criterion 1]
- [ ] [Criterion 2]
## Files
- Create: `path/to/new.ts`
- Modify: `path/to/existing.ts`
- Test: `tests/path.ts`
## Steps
1. [Specific action]
2. [Specific action]
## Verification
- Test: `npm test -- {pattern}`
| Type | Executor Rules |
|---|---|
backend | TDD mandatory (red→green→refactor) |
frontend | Anti-slop mandatory, reference existing |
mixed | Backend: TDD, Frontend: anti-slop |
memctx_save:
type: observation
title: {feature} Tasks
path: 60-observations/{feature}-tasks.md
tags: [sdlc, plan, {feature}]
plan_tracker_ide:
action: init
feature: "{feature}"
specPath: "docs/specs/{feature}/spec.md"
tasks:
- name: "Task 01: {name}"
type: backend
criteria: ["criterion 1", "criterion 2"]
- name: "Task 02: {name}"
type: frontend
criteria: ["criterion 1"]
plan_tracker_ide:
action: approve
phase: plan
summary: "{N} tasks created for {feature}"
git add docs/specs/{feature}/tasks/
git commit -m "docs: add task breakdown for {feature}"
Good: 15-60 min, single responsibility, independently testable.
Split if: Multiple unrelated changes, >3 files, >2 hours.
Merge if: <5 min, tightly coupled.
Plan complete: {N} tasks in
docs/specs/{feature}/tasks/Ready to execute? →
/skill:sdlc-execute