Home / othmanadi / planning-with-files · GitHub

planning-with-files SKILL.md skillA

planning-with-files from othmanadi/planning-with-files is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add othmanadi/planning-with-files/planning-with-files@v3.0.1-kiro

Pins v3.0.1-kiro in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: othmanadi/planning-with-files
Path: .kiro/skills/planning-with-files/SKILL.md
Versions recorded: 6
Latest version: v3.0.1-kiro, committed Sep 13, 2026
First version recorded: May 1, 2026
Size: 8,516 bytes
Repository stars: 27,556
License: MIT

Persistent file-based planning for multi-step AI-agent work. Keeps task_plan.md, findings.md, and progress.md on disk; Kiro skill instructions and steering state read selected project planning context. Recovery reads project planning files and their timestamps only, not agent transcript stores. This adapter registers no Stop hook, never requests continuation, and never runs commands declared in Markdown. The skill has no network upload path. Use for research or work needing 5+ tool calls.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# 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.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add othmanadi/planning-with-files/planning-with-files@sha256:877192e10e03e80b

The line at the top of this page pins the label v3.0.1-kiro, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_lgwtuclvj7yn6f2j.svg)](https://markdownregistry.com/a/art_lgwtuclvj7yn6f2j)

6 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 6 versions of this file, between May 1, 2026 and Sep 13, 2026, about one every 27 days.

version	committed	commit	size	audit
v3.0.1-kiro latest	2026-09-13	ae7e3ae	8,516 B	A	view · diff
v3.0.1-kiro	2026-08-30	d5d35e6	8,349 B	A	view · diff
v3.0.0-kiro	2026-08-30	7e55a06	8,349 B	A	view · diff
v3.0.0-kiro	2026-06-09	03ef8be	8,222 B	A	view · diff
v2.43.0-kiro	2026-05-26	577a1c5	8,223 B	A	view · diff
v2.32.0-kiro	2026-05-01	f7e8919	4,415 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (8516 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

othmanadi/planning-with-files · 27,556 stars · license MIT · pushed 2026-10-20 · branch master

API

GET https://markdownregistry.com/api/v1/artifacts/art_lgwtuclvj7yn6f2j
GET https://markdownregistry.com/api/v1/resolve?ref=othmanadi/planning-with-files/planning-with-files
GET https://markdownregistry.com/api/v1/blob/877192e10e03e80b974db846d54bb43c2bd235d5841f3129e619c8053e71f675

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.