- name
SKILL.md
स्किल फ़ाइल पब्लिशर की रिपॉज़िटरी में ही रहती है।
कॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add OthmanAdi/planning-with-files --skill planning-with-files -a cursor -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add OthmanAdi/planning-with-files --skill planning-with-files -a claude-code -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add OthmanAdi/planning-with-files --skill planning-with-files -a codex -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add OthmanAdi/planning-with-files --skill planning-with-files -a grok -yकॉपी किया गया संदेश Grok Bot चैट में भेजें। Bot यह SKILL.md GitHub से लाता है और उसे उन स्किल में जोड़ देता है जो आपके सभी Bot साझा करते हैं।
Install this skill: https://github.com/OthmanAdi/planning-with-files/tree/HEAD/.kiro/skills/planning-with-filesपब्लिशर से
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.
Kiro complements this with:
.kiro/steering/planning-context.md uses inclusion: auto and #[[file:.kiro/plan/…]] live references (Steering docs).Hooks are not bundled: project-level hooks affect every chat in the workspace. Prefer this skill + steering + the reminder block below.
From the workspace root:
sh .kiro/skills/planning-with-files/assets/scripts/bootstrap.sh
Windows (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).
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.mdand.kiro/plan/progress.mdto restore context.
.kiro/plan/task_plan.md — goal, phases, status.kiro/plan/progress.md — recent actions.kiro/plan/findings.md for research and decisionsIf .kiro/plan/ is missing, run STEP 0.
Summaries and planning-file mtimes (compare with git diff --stat if needed). This helper does not read Kiro or other agent transcript stores:
$(command -v python3 || command -v python) \
.kiro/skills/planning-with-files/assets/scripts/session-catchup.py "$(pwd)"
Windows:
python .kiro/skills/planning-with-files/assets/scripts/session-catchup.py (Get-Location)
Then reconcile planning files with the actual codebase.
From workspace root (defaults to .kiro/plan/task_plan.md):
sh .kiro/skills/planning-with-files/assets/scripts/check-complete.sh
pwsh -File .kiro/skills/planning-with-files/assets/scripts/check-complete.ps1
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 "$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.
Context Window = RAM (volatile, limited)
Filesystem = Disk (persistent, unlimited)
→ Anything important gets written to disk.
Never start a complex task without task_plan.md. Non-negotiable.
"After every 2 view/browser/search operations, IMMEDIATELY save key findings to text files."
This prevents visual/multimodal information from being lost.
Before major decisions, read the plan file. This keeps goals in your attention window.
After completing any phase:
in_progress → completeEvery error goes in the plan file. This builds knowledge and prevents repetition.
if action_failed:
next_action != same_action
Track what you tried. Mutate the approach.
When all phases are done but the user requests additional work:
task_plan.md (e.g., Phase 6, Phase 7)progress.mdATTEMPT 1: Diagnose & Fix
→ Read error carefully
→ Identify root cause
→ Apply targeted fix
ATTEMPT 2: Alternative Approach
→ Same error? Try different method
→ Different tool? Different library?
→ NEVER repeat exact same failing action
ATTEMPT 3: Broader Rethink
→ Question assumptions
→ Search for solutions
→ Consider updating the plan
AFTER 3 FAILURES: Escalate to User
→ Explain what you tried
→ Share the specific error
→ Ask for guidance
Kiro keeps its plan in .kiro/plan/. The canonical set-active-plan listing helper reads named plans under .planning/ and does not list or switch this Kiro plan.
Helper scripts (under assets/scripts/):
assets/scripts/bootstrap.sh — Idempotent workspace bootstrap. Creates .kiro/plan/ and .kiro/steering/planning-context.md.assets/scripts/session-catchup.py: Reports Kiro planning-file timestamps and summaries. It does not read agent transcript stores.assets/scripts/check-complete.sh -- Verify all phases in the active plan are complete.Use: multi-step work, research, refactors, anything that spans many tool calls.
Skip: one-off questions, tiny single-file edits.
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
---name: planning-with-filesdescription: Persistent file-based planning for multi-step AI-agent work. Keeps task_plan.md, findings.md, and progress.md…---# .kiro/skills/planning-with-files/SKILL.mdओवरव्यू
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.
FAQ
पब्लिशर से .kiro/skills/planning-with-files/SKILL.md डाउनलोड करें, या पाथ कॉपी करके रिपॉज़िटरी खोलें। PlugMCP स्किल को सूचीबद्ध करता है, फ़ाइल होस्ट नहीं करता।
पब्लिशर इसे https://github.com/OthmanAdi/planning-with-files पर रखता है।
Claude, Cursor, Codex और Grok Build वह SKILL.md पढ़ सकते हैं जिसे आप पब्लिशर की रिपॉज़िटरी से जोड़ते हैं। जब आप चैट में स्किल के GitHub फ़ोल्डर का लिंक भेजते हैं, तो Grok Bot उसे इंस्टॉल कर देता है।