doc-spec-autopilot

Included with Lifetime

$97 forever

Generate SPECs end-to-end from BDD/ADR, a prompt, or an IPLAN - detect input, generate the component spec, validate, and run the audit/fix cycle. Use to create or batch-create SPECs.

Design

What this skill does


# doc-spec-autopilot

## Purpose

Automated **SPEC generation pipeline**. From upstream BDD/ADR documents, a user
prompt, or an implementation plan (`IPLAN-*`), it analyzes the source, generates
a complete component SPEC, validates readiness, maintains `SPEC-00_index.md`, and
drives the audit↔fix cycle to a passing score — for one SPEC or a batch.

**Layer**: 6. **Upstream**: BDD/ADR (and the EARS/PRD/BRD chain), or a
prompt/IPLAN input. **Downstream**: a validated SPEC + index entry.

## Skill Dependencies

| Skill | Role |
|-------|------|
| `../doc-spec/SKILL.md` | SPEC structure and authoring rules (generation) |
| `../doc-spec-audit/SKILL.md` | quality gate (scoring + findings) |
| `../doc-spec-fixer/SKILL.md` | applies fixes from the audit report |
| `../doc-naming/SKILL.md` | ID standards (dash-form `SPEC-NN`) |

## Input Contract

Accepts: a target SPEC id/path; an upstream BDD/ADR id or path; a free-text
prompt; or an IPLAN path. 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 SPEC already exists (nested folder
`docs/06_SPEC/SPEC-NN_{slug}/`):

- **Missing** → *generate* mode (from BDD/ADR, prompt, or IPLAN).
- **Exists** → *review & fix* mode (audit, then fix if below threshold).

A `SPEC-NN` input is treated as the self type (review). A `BDD-NN`/`ADR-NN`
input is the upstream source: generate the matching SPEC if missing, else review.

## Workflow

1. **Input analysis** — classify the input (BDD/ADR / prompt / IPLAN), locate
   upstream material, and decide generate vs review-and-fix.
2. **Upstream readiness** — confirm the upstream ADR/BDD exist and are ready;
   reserve the next `SPEC-NN`.
3. **Generation** — produce the SPEC per `../doc-spec/SKILL.md`: Document Control
   first, all 8 sections in YAML, interfaces/data models/behavior at C4-L3,
   cumulative tags (`@brd @prd @ears @bdd @adr`), `@threshold` references for
   numbers, downstream `@tdd: TDD-NN` contract, diagram tags via
   `../charts-flow/SKILL.md`.
4. **Validation** — run `../doc-spec-audit/SKILL.md` from scratch.
5. **Audit ↔ fix cycle** — while score < threshold and iterations < max: run
   `../doc-spec-fixer/SKILL.md`, then re-audit. On pass, update
   `docs/06_SPEC/SPEC-00_index.md`; on exhausting iterations, flag for manual
   review.

## Execution Modes

- **Single** — one SPEC (generate or review-and-fix).
- **Batch** — multiple SPECs, processed in **chunks of 3** to bound context.
- **Dry-run** — report the planned actions (sections, IDs, upstream tags)
  without writing files.

## Quality Gates

- Generation does not complete until the audit passes (TDD-Ready score ≥
  threshold, 0 Tier-1 errors) or the iteration cap is hit (then: manual-review
  flag).
- The SPEC index is updated only after a SPEC passes.
- Fresh audit every cycle — no cached scores.

## Error Handling

| Situation | Action |
|-----------|--------|
| Referenced upstream ADR/BDD missing | stop; report the missing dependency |
| 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 SPEC |
| 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-spec/SKILL.md` · Audit: `../doc-spec-audit/SKILL.md` · Fix:
  `../doc-spec-fixer/SKILL.md`
- Authority: `${CLAUDE_PLUGIN_ROOT}/framework/layers/06_SPEC/SPEC-TEMPLATE.yaml`,
  `${CLAUDE_PLUGIN_ROOT}/framework/layers/06_SPEC/README.md`,
  `${CLAUDE_PLUGIN_ROOT}/framework/layers/06_SPEC/SPEC-00_index.TEMPLATE.md`

Files: 1

Size: 4.7 KB

Complexity: 13/100

Category: Design

Source: https://github.com/vladm3105/aidoc-flow-framework/tree/main/platforms/claude-code-plugin/skills/doc-spec-autopilot

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts