ilk-looplisted

Resume and drive a multi-step execution plan organised as one MASTER plan + several sub-plans, each step recoverable from disk. Use when the user says "/ilk", "resume the loop", "continue the plan", "next step", or refers to files under `docs/plans/MASTER-*.md`. Also use to set up the convention in a new project, add a new sub-plan, or check loop status. Works across Cursor, Claude Code, and Codex.
inluck-net/ilk-skills · ★ 0 · AI & Automation · score 66

Install: claude install-skill inluck-net/ilk-skills

# ilk Loop — Master + Sub-Plan execution convention A lightweight, file-driven workflow for breaking large changesets into small, resumable steps. Each loop iteration runs in a fresh chat session so the agent never grows past its context window. ## When to use - The user invokes any of the slash commands `/ilk`, `/ilk-plan`, or `/ilk-lark` (Cursor, Claude Code, or Codex). - The user says: "resume the loop", "continue the plan", "next step", "ship the next sub-plan", "where are we", "loop status". - The user asks to **plan** something (turn a task description or batch of tickets into master + sub-plans). - The user asks to set up ilk-loop in a new project. - The user asks to add a new sub-plan to an existing master. - Codex users may say: "continue the ilk loop", "run the next step", "plan this task", or "ilk plan" without a slash prefix. ## Architecture `<skill-root>` below means the installed skills base directory — `~/.cursor/skills/` (Cursor), `~/.claude/skills/` (Claude Code), or `~/.codex/skills/` (Codex) — depending on the host agent. The companion `commands/` directory is its sibling, e.g. `~/.cursor/commands/`. ``` <skill-root>/ilk-loop/ SKILL.md ← this file scripts/ loop_status.py ← universal status checker ilk_paths.py ← path resolver (external plans dir) templates/ README.md ← scaffold for external plans dir README subplan-template.md