# create-plan

> Create a plan folder with frontmatter, roadmap link, nav entry, and validation

- Author: Andrew Holder
- Repository: drewswiredin/chappie
- Version: 20260207192122
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-08
- Source: https://github.com/drewswiredin/chappie
- Web: https://mule.run/skillshub/@@drewswiredin/chappie~create-plan:20260207192122

---

---
name: create-plan
description: Create a plan folder with frontmatter, roadmap link, nav entry, and validation
domain: Orchestrator
scope: internal
user-invocable: false
allowed-tools: Write, Edit, Read, Bash, Glob
---
# Create Plan

Plans are **operator-initiated**. Never create one unprompted.

## Process

1. **Create folder**: `docs/environment/plans/<slug>/`
2. **Create index.md** with frontmatter:

```yaml
---
title: [Operator's plan name]
status: active
created: [today's date]
updated: [today's date]
roadmap: <roadmap-slug>  # optional — folder name, NOT filename
summary: [one-liner]     # optional — shown in SessionStart output
target: YYYY-MM-DD       # optional
---
```

3. **Add to mkdocs.yml** nav under Plans, before Archive:

```yaml
- Plans:
    - Overview: environment/plans/index.md
    - [Name]: environment/plans/<slug>/index.md   # ← add here
    - Archive: environment/plans/archive/index.md
```

4. **Validate**: `bash scripts/validate-consistency.sh && mkdocs build --strict`

## Gotchas

- `roadmap` field = folder name (e.g., `cloud-migration`), not a filename or path
- Standalone plans omit the `roadmap` field entirely — don't set it to empty string
- `summary` is shown after the plan title in SessionStart output — keep it under 60 chars
- Multiple plans can reference the same roadmap — the roadmap doesn't list its plans