planning-with-files

Files (13)

• SKILL.md
• bootstrap.ps1 · assets/scripts/
• bootstrap.sh · assets/scripts/
• check-complete.ps1 · assets/scripts/
• check-complete.sh · assets/scripts/
• session-catchup.py · assets/scripts/
• findings.md · assets/templates/
• planning-context.md · assets/templates/
• progress.md · assets/templates/
• task_plan.md · assets/templates/
• manus-principles.md · references/
• planning-rules.md · references/
• planning-templates.md · references/

SKILL.md (first lines)

# Planning with Files (Kiro)

Work like **Manus**: use persistent markdown as your **working memory on disk** while the model context behaves like volatile RAM. Deep background: [references/manus-principles.md](references/manus-principles.md).

Kiro complements this with:

- **Agent Skills** (this file) — progressive disclosure when the task matches the description.  
- **Steering** — after bootstrap, `.kiro/steering/planning-context.md` uses `inclusion: auto` and `#[[file:.kiro/plan/…]]` live references ([Steering docs](https://kiro.dev/docs/steering/)).

**Hooks are not bundled:** project-level hooks affect every chat in the workspace. Prefer this skill + steering + the reminder block below.

---

## STEP 0 — Bootstrap (once per workspace)

From the **workspace root**:

```bash
sh .kiro/skills/planning-with-files/assets/scripts/bootstrap.sh
```

Windows (PowerShell):

```powershell
pwsh -ExecutionPolicy RemoteSigned -File .kiro/skills/planning-with-files/assets/scripts/bootstrap.ps1
```

Creates:

- `.kiro/plan/task_plan.md`, `findings.md`, `progress.md`
- `.kiro/steering/planning-context.md` (auto + `#[[file:.kiro/plan/…]]`)

Idempotent: existing files are not overwritten.

**Import as a workspace skill (optional):** Kiro → *Agent Steering & Skills* → *Import a skill* → choose this `planning-with-files` folder ([Skills docs](https://kiro.dev/docs/skills/)).

---

## STEP 1 — Persistent reminder (after skill activation)

Append the following block to the **end of your reply**, and repeat it at the **end of subsequent replies** while this planning session is active:

> `[Planning Active]` Before each turn, read `.kiro/plan/task_plan.md` and `.kiro/plan/progress.md` to restore context.

---

## STEP 2 — Read plan every turn (while active)

1. Read `.kiro/plan/task_plan.md` — goal, phases, status  
2. Read `.kiro/plan/progress.md` — recent actions  
3. Use `.kiro/plan/findings.md` for research and decisions  

If `.kiro/plan/` is missing, run STEP 0.

---

## STEP 3: Project-file catchup (after a long gap or suspected drift)

Summaries and planning-file mtimes (compare with `git diff --stat` if needed). This helper does not read Kiro or other agent transcript stores:

```bash
$(command -v python3 || command -v python) \
  .kiro/skills/planning-with-files/assets/scripts/session-catchup.py "$(pwd)"
```

Windows:

```powershell
python .kiro/skills/planning-with-files/assets/scripts/session-catchup.py (Get-Location)
```

Then reconcile planning files with the actual codebase.

---

## Optional — Phase checklist

From workspace root (defaults to `.kiro/plan/task_plan.md`):

```bash
sh .kiro/skills/planning-with-files/assets/scripts/check-complete.sh
```

```powershell
pwsh -File .kiro/skills/planning-with-files/assets/scripts/check-complete.ps1
```

---

## New plan creation contract

For a new Kiro task, run STEP 0 bootstrap before implementation. Set `PWF_SKILL_DIR` to the directory containing this SKILL.md, then run from the workspace root:

```sh
sh "$PWF_SKILL_DIR/assets/scripts/bootstrap.sh"
# After filling in the selected plan, validate its explicit path:
sh "$PWF_SKILL_DIR/assets/scripts/check-complete.sh" --validate .kiro/plan/task_plan.md
```

PowerShell equivalents are `assets/scripts/bootstrap.ps1` and `assets/scripts/check-complete.ps1 -Validate -PlanFile .kiro/plan/task_plan.md`.

Keep each phase as `### Phase N: Name` with exactly one `**Status:** pending`, `**Status:** in_progress`, or `**Status:** complete` line. A `## Phases` checklist or numbered summary alone is not trackable. Preserve these markers when tailoring the generated plan; do not replace the skeleton with a compact custom format. Validation must succeed before substantive work and after changing phase structure. This checks format, not task completion or attestation.

Reuse existing plans without overwriting them. If an existing plan fails validation, report the issue for its owner to review; do not automatically rewrite it. If helpers cannot run, copy the shipped template exactly and state that native validation is unavailable.

## The Core Pattern

```
Context Window = RAM (volatile, limited)
Filesystem = Disk (persistent, unlimited)

→ Anything important gets written to disk.
```

## File Purposes

| File | Purpose | When to Update |
|------|---------|----------------|
| `task_plan.md` | Phases, progress, decisions | After each phase |

From OthmanAdi/planning-with-files, MIT.

More from OthmanAdi/planning-with-files