# Create Structured Plan Directories

Complex projects can lose context when plans live in loose notes. This skill creates a PLAN.md index and numbered task files with checklists.

## Install

```bash
npx skillstore add diversioteam/plan-directory
```

## Metadata

- Status: approved
- Slug: diversioteam-plan-directory
- Skillstore revision: r1
- Version status: missing
- Tree hash: 605a475189ad9cbd371fdfafbee971170930495a770e83c31bbfc20720103119
- Author: DiversioTeam
- GitHub username: DiversioTeam
- License: MIT
- Repository: https://github.com/DiversioTeam/agent-skills-marketplace/tree/main/plugins/plan-directory/skills/plan-directory
- Ref: c579efd02184f1128d6741d16e6c8d951d7d4208
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem
- Quality score: 74
- Public page: https://skillstore.pages.dev/skills/diversioteam-plan-directory
- Manifest: https://skillstore.pages.dev/api/skills/diversioteam-plan-directory/manifest

## Capabilities

- Creates a PLAN.md master index for a project or feature plan.
- Creates numbered task files using three digit prefixes and slug names.
- Adds required sections for goals, dependencies, scope, checklist, tests, and completion criteria.
- Updates existing plans while preserving assigned task numbers.
- Tracks completed work through Markdown checkboxes in task files and the index.
- Documents blockers, dependencies, parallel work, and optional retrospectives.

## Use Cases

- Plan a Feature Build: Break a feature into numbered tasks with dependencies, tests, and completion criteria.
- Coordinate a Migration: Create a repeatable migration plan with locked decisions, blockers, and staged verification steps.
- Maintain Project Progress: Update an existing plan as tasks finish, change, split, or become blocked.

## Prompt Templates

### Create a Basic Plan

```
Create a plan directory for my feature. Title: User Authentication. Slug: user-auth. Tasks: user model, login, password reset, tests.
```

### Use a Specific Location

```
Create a plan in docs/plans/billing-redesign. Use the slug billing-redesign. Include tasks for data model, UI, API, migration, and QA. Keep Stripe as the payment provider.
```

### Update an Existing Plan

```
Update the existing user-auth plan. Add a new task for Google OAuth, preserve all current task numbers, and mark it dependent on JWT setup.
```

### Design a Complex Execution Plan

```
Create a migration plan for moving from REST to GraphQL. Include backend schema work, client migration, compatibility testing, rollout gates, rollback criteria, and parallel tasks where safe.
```

## Limitations

- It writes planning documents, not application code or implementation changes.
- It needs a title, slug, and task list to produce a useful plan.
- It does not prove that generated test commands pass.
- It can edit files in the selected plan location, so paths should be reviewed.

## Best Practices

- Provide a clear title, slug, task list, and target location before generating files.
- Keep PLAN.md as an index and put detailed work inside numbered task files.
- Review generated dependencies and test steps before using the plan for execution.

## Anti Patterns

- Do not use this skill for a single informal todo list.
- Do not renumber existing tasks after work has started.
- Do not ask it to run implementation tests unless you also authorize that work separately.

## Security Audit

- Audited at: 2026-07-05T13:25:14.761\+00:00
- Summary: All 81 static findings were reviewed against SKILL.md. The backtick, path traversal, and reconnaissance alerts are false positives from Markdown examples, template paths, and test text. A low severity semantic issue remains because the front matter grants Bash even though the workflow only needs file and glob operations.

## Stats

- Views: 275
- Downloads: 8
- Favorites: 0
- Popularity score: 0