From io
Use for small features (up to a day, 1–2 areas) under `docs/<feature>/` — bootstrapping, advancing phases, lifting decisions, optional review. Mirrors `io:develop-feature` shape but drops phase/topic/section ceremony. Graduates to `io:develop-feature` when scope grows. Invoke with arg `review` to act as the Review Agent.
How this skill is triggered — by the user, by Claude, or both
Slash command
/io:develop-mini-featureThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Drive a lightweight explore → approach → build cycle for a small feature. The user contributes substance; the skill handles ceremony — directory creation, lift bookkeeping, optional Review Agent spawning, and graduation to `io:develop-feature` when the scope outgrows mini.
Drive a lightweight explore → approach → build cycle for a small feature. The user contributes substance; the skill handles ceremony — directory creation, lift bookkeeping, optional Review Agent spawning, and graduation to io:develop-feature when the scope outgrows mini.
This skill is suggest-only. Wait for explicit invocation; the agent may recommend it when the conversation enters lifecycle territory.
Do not engage for: typo fixes, single-line changes, bugfixes with a clear root cause (use practo:fix-sentry or practo:debug instead), pure refactors (use practo:refactor), or tasks that finish in under an hour.
io:develop-featureUse io:develop-mini-feature (this skill) when:
Use io:develop-feature when:
If a mini feature grows past the ceiling, route to procedures/graduate.md — one-way migration into the full skill's shape.
OBJECTIVE.md, PLAN.md, DECISIONS.md entries (via lift.md), and code. In review, appends > **Coding Agent response** blocks under each finding in REVIEW.md.REVIEW.md. Entered by args="review". Delegates the review machinery to io:develop-feature/procedures/code-review.md.One role per session, selected by the skill argument:
review → Review Agent.Invocation: Skill(skill="io:develop-mini-feature", args="review"). The Review Agent is auto-spawned by procedures/review.md Path A; users normally never invoke review directly.
Run on every invocation:
ls docs/ — locate feature dirs (dirs containing OBJECTIVE.md). 0 → bootstrap mode. 1 → auto-pick. 2+ → ask which one.exploration/, spec/, or build/ subdirs exist, this feature is tracked by io:develop-feature. Surface: "This feature is on the full skill. Invoke io:develop-feature instead." Stop.PLAN.md:
start and first exploration content.## Exploration notes filled, ## Approach empty → exploration phase.## Approach filled, ## Build checklist empty → approach phase.[ ] items → build phase.[x] → build complete.<!-- Review: enabled (Review Agent) --> → REVIEW.md exists and is the review surface.## Review notes).If PLAN.md is malformed or unreadable, surface and ask. Do not guess.
procedures/start.mdprocedures/advance.mdprocedures/lift.md (immediate-lift path)procedures/review.md (Path A: Coding Agent)args="review" → procedures/review.md (Path B: Review Agent)procedures/graduate.mddocs/<feature>/OPEN-QUESTIONS.md (create on first one); no procedure needed — the conversational flow handles it.A decision in ## Exploration notes, ## Approach, ## Review notes, or REVIEW.md qualifies for DECISIONS.md if all three hold:
Sweep happens at every advance.md phase transition; immediate lift can fire any turn. DECISIONS.md is lazy — created on first lift. Per-feature monotonic #N, numbers never reuse. The inline callout/tag stays in place; the DECISIONS.md entry carries the distilled "decision + why" plus a backlink (Source: line). One-way pointer: central → inline.
Canonical reference: io:develop-feature/reference/lift-criteria.md. Detailed procedure: procedures/lift.md.
Mid-work issue, unclear destination:
Review comment callout in the active PLAN.md section (or decision: tag in review).OPEN-QUESTIONS.md (create on first one).If the issue is owned by another team / another codebase, or is a "do later" cleanup, mini has no equivalent of MIGRATION-CHECKLIST.md or TECH-DEBT.md. Either fold into OPEN-QUESTIONS.md or, if persistent tracking matters, graduate.
Canonical reference: io:develop-feature/reference/issue-routing.md.
ls docs/, read OBJECTIVE.md and PLAN.md. State files are the cursor; never maintain a sidecar.procedures/graduate.md.OBJECTIVE.md — confirm with user before any edit after start.md.PLAN.md — Coding Agent edits freely.OPEN-QUESTIONS.md — Coding Agent adds entries freely; resolving requires user confirmation. Shape on creation: io:develop-feature/templates/open-questions.md.DECISIONS.md — Coding Agent appends new entries via lift.md only; never rewrites existing entries.REVIEW.md — Review Agent owns the file. Coding Agent appends only > **Coding Agent response** blocks under findings (shape: io:develop-feature/reference/doc-ownership.md).Lifecycle moves (graduate's git rm of PLAN.md and REVIEW.md) are exempt from ownership rules — procedures/graduate.md performs them.
procedures/
start.md — bootstrap a feature dir
advance.md — phase transition + lift sweep
lift.md — append one decision to DECISIONS.md
review.md — opt-in review (Path A: Coding Agent; Path B: Review Agent)
graduate.md — migrate to io:develop-feature shape
templates/
objective.md — same shape as io:develop-feature's, minus "Systems in play"
plan.md — Exploration notes / Approach / Build checklist / Review notes
Each procedure is self-contained: preconditions, steps, errors, postconditions. Read the procedure when routing to it. For finding/callout shapes, read directly from io:develop-feature/templates/ — mini does not duplicate them.
npx claudepluginhub mayankdharwa/helios --plugin ioGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.