corestory-frontier/specspec-skills
Create and review SpecSpec designs, then build reference applications with code-derived L0 evidence.
Generate a source-derived SpecSpec L0-L4 bundle from an existing codebase. Audit reachable behavior and optionally compare it with a supplied spec, reporting implementation and intent gaps.
Document actual source files as SpecSpec L0 Source File concepts from an existing codebase. Use for code inventory, symbols, dependencies, and line-anchored evidence.
Derive SpecSpec L1 Module documents from an existing codebase and L0 source evidence. Use when documenting actual package responsibilities and module dependencies.
Derive SpecSpec L2 Component documents from an existing codebase and lower-layer evidence. Use when documenting actual subsystem boundaries and ownership.
Derive SpecSpec L3 system concepts from an existing codebase. Use for observed data, interfaces, workflows, controls, runtime, and architecture evidence.
Infer SpecSpec L4 Product Overview and Capabilities from an existing codebase with source-backed behavior and clear uncertainty about product intent.
Review a code-derived SpecSpec L0-L4 bundle against source and an optional reference spec for accuracy, coverage, traceability, and implementation gaps. Read-only.
Correct a SpecSpec L4-L1 design from a review-specspec-design findings report. Use to resolve confirmed structural, traceability, provenance, consistency, or architecture findings while preserving supplied intent.
Create a complete top-down SpecSpec L4-L1 design from a short software application description. Use when the user wants the full SpecSpec design workflow instead of one layer.
Create or revise SpecSpec L1 Module documents from a complete set of L2 Component documents and their L3 context. Use for top-down module design that stops before L0 source-file documentation. Do not use this skill without L2 inputs or to describe implemented code.
Create or revise SpecSpec L2 Component documents from a complete set of L3 system documents. Use for top-down architectural decomposition before L1 or L0 design. Do not use this skill without L3 inputs or to document implemented code.
Create or revise SpecSpec L3 system documents from a complete set of L4 Product Overview and Capability files. Use for top-down system design before L2, L1, or L0 decomposition. Do not use this skill without L4 inputs or to document implemented code.
Create or revise SpecSpec L4 Product Overview and Capability files from a short software application description. Use for top-down product specification before L3, L2, or L1 decomposition. Do not use this skill to document code or create lower layers.
Build a new reference application from approved SpecSpec L4-L1 documents. Obtain stack approval, deliver a runnable first version, test every Capability behavior and acceptance criterion, derive L0 from tested code, and obtain an independent L0-L4 review. Use for new applications, not changes to an existing application.
Review a complete top-down SpecSpec L4-L1 design for architectural gaps, contradictions, weak boundaries, and broken traceability. Use after generation or before implementation. This skill reports findings and does not edit documents.