documentation-architect

Transform concept development artifacts into INCOSE-compliant formal requirements. AI-assisted requirements development with hybrid quality checking (16 deterministic + 9 semantic INCOSE GtWR v4 rules), verification planning, bidirectional traceability, gap analysis against concept architecture, assumption lifecycle management, and ReqIF export. Organized around functional blocks from concept development. Includes cross-cutting notes registry, need/requirement split workflow, gap discovery agent, assumption tracker, 5 specialized agents (quality-checker, tpm-researcher, skeptic, gap-analyst, document-writer), 16 scripts, 10 commands, and hooks for automatic state updates. Use when developing requirements, formalizing needs, writing specifications, building traceability, analyzing coverage gaps, managing assumptions, or preparing for systems engineering reviews.

Stream long-form content to markdown files with resume capability and context preservation

Walk through the NASA Phase A concept development lifecycle: ideation, problem definition, black-box architecture, drill-down with gap analysis, and document generation. Produces concept documents and solution landscape summaries with cited research. Includes 7 specialized agents (ideation, problem analysis, architecture, domain research, gap analysis, skeptic verification, document writing), 6 scripts (session management, source/assumption tracking, web research with crawl4ai), 9 commands, hooks for automatic state updates, and tiered research tool detection. Use when developing a concept, exploring a new idea, brainstorming a system concept, running Phase A, creating a concept document, or conducting feasibility studies.

Project-focused specification and task management with PLANS taxonomy, ADR-style architecture decisions, SMART acceptance criteria, SEAMS-enhanced clarification, tech-specific designer agents, anti-pattern detection (50 patterns across 5 tech stacks), 4-level verification (stub detection + wiring checks), execution orchestration (deviation rules, checkpoint taxonomy, auth gates, session continuity), specialized analysis agents, git checkpoints, mandatory approval gates, and session-memory hooks. Outputs to speckit/ directory.

Deep test, analyze, and audit Claude skills. Use this skill whenever the user wants to test a skill's behavior, analyze how it uses the Claude API, inspect inputs/outputs from scripts, or run security and code review audits against skill scripts. Trigger on: "test my skill", "analyze this skill", "audit skill scripts", "review skill for security issues", "what does this skill actually do when it runs", "inspect API calls from skill", "run a skill through its paces", "check my skill for bugs or vulnerabilities". Also trigger when the user shows you a SKILL.md and asks you to evaluate, critique, or stress-test it.