christopherlouet/claude-base / .claude/skills/work-plan
work-plan
VerifiedPlan the implementation of a feature. Use when the user wants to plan, architect, define an approach, or before coding a complex feature.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.2 KB |
| examples/planning-example.md | markdown | 3.1 KB |
SKILL.md
View on GitHub---
name: work-plan
description: Plan the implementation of a feature. Use when the user wants to plan, architect, define an approach, or before coding a complex feature.
disable-model-invocation: true
---
# Plan an Implementation
## Objective
Define an action plan BEFORE coding. The plan must be validated before implementation.
## Native features first
Claude Code natively provides the planning *mechanism*: **plan mode** (`/plan [description]`) keeps Claude read-only until you approve a plan, and the built-in **Plan** sub-agent researches the codebase for it. Use them to run the planning.
**This skill's delta is the template the plan is held to**: the files to create and modify, the identified risks with their mitigations, and the explicit validation before any code, as the Plan step of the Explore → Specify → Plan → TDD flow. Fill it from inside plan mode.
## Instructions
### 1. Understand the request
**Questions to clarify:**
- What is the business objective?
- What are the acceptance criteria?
- Are there any technical constraints?
- What is the priority/deadline?
### 2. Analyze the existing code
```bash
# Search for similar code
grep -rn "similar_pattern" --include="*.ts" | head -20
# Identify dependencies
cat package.json | grep -A 20 '"dependencies"'
```
### 3. Define the architecture
**Decisions to make:**
- Where to place the new code?
- Which patterns to use?
- Which interfaces to create?
- How to handle errors?
### 4. List the tasks
Break down into atomic tasks of 1-2h max.
## Plan template
```markdown
## Plan: [Feature name]
### Objective
[Description in 1-2 sentences]
### Files to create
| File | Description |
|---------|-------------|
| `src/xxx.ts` | [Role] |
### Files to modify
| File | Modifications |
|---------|---------------|
| `src/yyy.ts` | [Changes] |
### Tests to write
- [ ] Nominal case test
- [ ] Edge cases test
- [ ] Error test
### Implementation steps
1. [ ] [Task 1]
2. [ ] [Task 2]
3. [ ] [Task 3]
### Identified risks
| Risk | Mitigation |
|--------|------------|
| [Risk 1] | [Solution] |
### Dependencies
- [ ] [Prerequisite 1]
```
## Rules
- NEVER code without a validated plan
- One plan = one feature
- Estimate complexity, not time
- Identify risks BEFORE
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |