doc-iplan-autopilot
Generate IPLANs end-to-end from a SPEC/TDD, a prompt, or an existing IPLAN - detect input, plan a test-first file manifest, generate, validate, and run the audit/fix cycle. Use to create or batch-create IPLANs.
What this skill does
# doc-iplan-autopilot
## Purpose
Automated **IPLAN generation pipeline**. From a SPEC/TDD component, a user
prompt, or an existing IPLAN, it analyzes the source, plans a test-first file
manifest, generates a complete IPLAN, validates CODE-readiness, maintains
`IPLAN-00_index.yaml`, and drives the audit↔fix cycle to a passing score — for
one IPLAN or a batch.
**Layer**: 8 (final doc layer; downstream is Code). **Upstream**: SPEC/TDD,
prompt, or existing IPLAN input. **Downstream**: a validated IPLAN + index entry.
This autopilot generates **permanent** IPLANs only (one per SPEC/TDD component).
Temporary bugfix plans are authored manually via `../doc-iplan/SKILL.md` and are
not registered in the index.
## Skill Dependencies
| Skill | Role |
|-------|------|
| `../doc-iplan/SKILL.md` | IPLAN structure and authoring rules (generation) |
| `../doc-iplan-audit/SKILL.md` | quality gate (CODE-Ready scoring + findings) |
| `../doc-iplan-fixer/SKILL.md` | applies fixes from the audit report |
| `../doc-naming/SKILL.md` | document/element-ID standards |
## Input Contract
Accepts: a target IPLAN id/path; a SPEC or TDD id/path; a free-text prompt; or an
existing IPLAN path. Precedence: explicit IPLAN > SPEC/TDD upstream > prompt.
Optional: score threshold (default 90), max fix iterations (default 3), batch
list. With no explicit input, treat the request as a prompt.
## Smart Document Detection
For each target, check whether the IPLAN already exists
(`docs/08_IPLAN/IPLAN-NN_*.yaml`):
- **Missing** → *generate* mode (from the SPEC/TDD component).
- **Exists** → *review & fix* mode (audit, then fix if below threshold).
A SPEC-NN or TDD-NN input maps to its IPLAN-NN; generate if missing, otherwise
review. Determine plan type (permanent vs temporary) from the source — this
autopilot proceeds only for permanent plans.
## Workflow
1. **Input analysis** — classify the input (SPEC/TDD / prompt / existing IPLAN),
locate the upstream component, and decide generate vs review-and-fix.
2. **Manifest planning** — verify the source TDD/SPEC is IPLAN-Ready ≥ threshold;
plan the test-first file order and identify file dependencies; reserve the
next `IPLAN-NN`.
3. **Generation** — produce the IPLAN per `../doc-iplan/SKILL.md`: Document
Control first, all 6 sections, test-first file manifest, execution commands,
implementation contracts when 3+ files share interfaces, seeded session
handoff, cumulative tags (`@brd @prd @ears @bdd @adr @spec @tdd`), and an
empty `code_inventory`. Diagrams via `../charts-flow/SKILL.md`.
4. **Validation** — run `../doc-iplan-audit/SKILL.md` from scratch.
5. **Audit ↔ fix cycle** — while score < threshold and iterations < max: run
`../doc-iplan-fixer/SKILL.md`, then re-audit. On pass, update
`docs/08_IPLAN/IPLAN-00_index.yaml`; on exhausting iterations, flag for manual
review.
## Execution Modes
- **Single** — one IPLAN (generate or review-and-fix).
- **Batch** — multiple IPLANs, processed in **chunks of 3** to bound context;
generate plans for upstream components before dependent ones.
- **Dry-run** — report the planned actions (type, file manifest, IDs) without
writing files.
## Quality Gates
- Generation does not complete until the audit passes (CODE-Ready ≥ threshold, 0
Tier-1 errors) or the iteration cap is hit (then: manual-review flag).
- The IPLAN index is updated only after a plan passes.
- Fresh audit every cycle — no cached scores.
## Error Handling
| Situation | Action |
|-----------|--------|
| Source SPEC/TDD below IPLAN-Ready threshold | stop; report the upstream gap (fix upstream first) |
| Max iterations reached below threshold | write reports, flag for manual review, continue batch |
| Source input ambiguous | fall back to prompt mode; record assumptions in the IPLAN |
| Write/permission error | log, skip the item, continue the batch |
## Adaptation
Before applying defaults, read the project adaptation profile
(`.aidoc/profile.yaml`) and apply it in both the generation and the internal
audit/fix phases. Honor `section_toggles`, `active_layers`, `audit_threshold`
(raise-only — stricter only), and `glossary`. Ignore any unknown or
out-of-surface key; absent a profile, use framework defaults.
Authority: `${CLAUDE_PLUGIN_ROOT}/framework/governance/ADAPTATION.md`.
## Related Resources
- Create: `../doc-iplan/SKILL.md` · Audit: `../doc-iplan-audit/SKILL.md` · Fix:
`../doc-iplan-fixer/SKILL.md`
- Authority: `${CLAUDE_PLUGIN_ROOT}/framework/layers/08_IPLAN/IPLAN-TEMPLATE.yaml`,
`${CLAUDE_PLUGIN_ROOT}/framework/layers/08_IPLAN/README.md`,
`${CLAUDE_PLUGIN_ROOT}/framework/layers/08_IPLAN/IPLAN-00_index.TEMPLATE.yaml`
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.