How do I install the Plan skill?

Run npx skillmds@latest add peopleforrester/plan in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Plan skill do?

Create a detailed implementation plan before coding It is listed under Productivity on SkillMD.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Plan?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

peopleforrester (@peopleforrester) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Plan by peopleforrester — Agent Skill

Name: Plan
Author: peopleforrester

File contents

/plan - Strategic Planning

Create a detailed implementation plan before coding.

Usage

/plan [feature or task description]

Examples

/plan user authentication with OAuth
/plan refactor the payment module
/plan add caching to API endpoints

Workflow

When invoked, follow this planning process:

1. Requirements Gathering

Ask clarifying questions:

What is the desired outcome?
What are the constraints (time, tech stack, compatibility)?
Are there existing patterns to follow?
What are the acceptance criteria?

2. Research Phase

Before proposing solutions:

Review relevant existing code
Check for similar implementations in the codebase
Identify dependencies and potential conflicts
Note any technical debt that might be affected

3. Design Options

Present 2-3 approaches with trade-offs:

## Option A: [Name]
**Approach**: [Brief description]
**Pros**: [Benefits]
**Cons**: [Drawbacks]
**Effort**: [Relative complexity]

## Option B: [Name]
...

4. Recommended Plan

After user selects approach, create detailed plan:

## Implementation Plan: [Feature Name]

### Phase 1: Setup
- [ ] Task 1
- [ ] Task 2

### Phase 2: Core Implementation
- [ ] Task 3
- [ ] Task 4

### Phase 3: Testing
- [ ] Unit tests for X
- [ ] Integration tests for Y

### Phase 4: Documentation
- [ ] Update README
- [ ] Add inline documentation

### Files to Modify
- `src/auth/oauth.ts` - Add OAuth provider
- `src/config/auth.ts` - Add configuration
- `tests/auth/oauth.test.ts` - Add tests

### Dependencies
- [ ] Install `oauth-library`
- [ ] Configure environment variables

### Risks & Mitigations
| Risk | Mitigation |
|------|------------|
| [Risk 1] | [How to address] |

5. Confirmation

Before proceeding:

Summarize the plan
Confirm with user
Get approval to begin implementation

Output Format

The plan should be:

Actionable (specific tasks, not vague goals)
Ordered (dependencies respected)
Testable (clear acceptance criteria)
Documented (files and changes listed)

Tips

Break large features into smaller phases
Identify the minimal viable implementation first
Consider rollback strategies for risky changes
Note integration points with existing systems

---name: plandescription: Create a detailed implementation plan before coding---# /plan - Strategic PlanningCreate a detailed implementation plan before coding.## Usage```/plan [feature or task description]```## Examples```/plan user authentication with OAuth/plan refactor the payment module/plan add caching to API endpoints```## WorkflowWhen invoked, follow this planning process:### 1. Requirements GatheringAsk clarifying questions:- What is the desired outcome?- What are the constraints (time, tech stack, compatibility)?- Are there existing patterns to follow?- What are the acceptance criteria?### 2. Research PhaseBefore proposing solutions:- Review relevant existing code- Check for similar implementations in the codebase- Identify dependencies and potential conflicts- Note any technical debt that might be affected### 3. Design OptionsPresent 2-3 approaches with trade-offs:```markdown## Option A: [Name]**Approach**: [Brief description]**Pros**: [Benefits]**Cons**: [Drawbacks]**Effort**: [Relative complexity]## Option B: [Name]...```### 4. Recommended PlanAfter user selects approach, create detailed plan:```markdown## Implementation Plan: [Feature Name]### Phase 1: Setup- [ ] Task 1- [ ] Task 2### Phase 2: Core Implementation- [ ] Task 3- [ ] Task 4### Phase 3: Testing- [ ] Unit tests for X- [ ] Integration tests for Y### Phase 4: Documentation- [ ] Update README- [ ] Add inline documentation### Files to Modify- `src/auth/oauth.ts` - Add OAuth provider- `src/config/auth.ts` - Add configuration- `tests/auth/oauth.test.ts` - Add tests### Dependencies- [ ] Install `oauth-library`- [ ] Configure environment variables### Risks & Mitigations| Risk | Mitigation ||------|------------|| [Risk 1] | [How to address] |```### 5. ConfirmationBefore proceeding:- Summarize the plan- Confirm with user- Get approval to begin implementation## Output FormatThe plan should be:- Actionable (specific tasks, not vague goals)- Ordered (dependencies respected)- Testable (clear acceptance criteria)- Documented (files and changes listed)## Tips- Break large features into smaller phases- Identify the minimal viable implementation first- Consider rollback strategies for risky changes- Note integration points with existing systems

Frequently asked questions

Plan