Loading...
Loading...
Use after brainstorming/design phase to create detailed implementation plans. Creates step-by-step plans clear enough for execution by any developer.
npx skill4agent add bbeierle12/skill-mcp-claude writing-plansdocs/plans/YYYY-MM-DD-<feature-name>.md# [Feature Name] Implementation Plan
> **For Claude:** Use executing-plans skill to implement this plan task-by-task.
## Overview
Brief description of what we're building and why.
## Prerequisites
- [ ] Dependency 1 installed
- [ ] Service 2 running
- [ ] Access to X configured
## Tasks
### Task 1: [Descriptive Name]
**File:** `path/to/file.ts`
**Test:** `path/to/file.test.ts`
#### Test First (RED)
```typescript
// Exact test code to write
describe('FeatureName', () => {
it('should do specific thing', () => {
// Arrange
// Act
// Assert
});
});// Exact implementation code
export function featureName() {
// Implementation
}npm test -- --grep "FeatureName"
# Expected: 1 passing# Commands to run
npm run test:integrationgit revert HEAD
## Plan Quality Checklist
### Every Task Must Have:
- [ ] Exact file paths
- [ ] Complete code (not "add validation")
- [ ] Test written BEFORE implementation
- [ ] Verification command with expected output
- [ ] Clear success criteria
### Plan Must Include:
- [ ] Prerequisites listed
- [ ] Tasks in dependency order
- [ ] Integration test at end
- [ ] Rollback instructions
## Writing Guidelines
### Be Explicit
❌ "Add error handling"
✅ "Wrap the API call in try/catch, log errors with context, return null on failure"
### Be Complete
❌ "Update the config"
✅ ```json
{
"setting": "value",
"newSetting": "newValue"
}## Remember
- Exact file paths always
- Complete code in plan (not "add validation")
- Exact commands with expected output
- DRY, YAGNI, TDD, frequent commits