Generate design artifacts from specs with a three-level workflow.
npx skills add https://github.com/zot/frictionless --skill mini-spec
Please help me install this Agent Skill. Skill: mini-spec Source: https://github.com/zot/frictionless/tree/main/.claude/skills/mini-spec Command: npx skills add https://github.com/zot/frictionless --skill mini-spec
Mini-spec provides a compact, repeatable framework to capture human specs, translate them into design artifacts, and track traceability across specs, design, and code, reducing misalignment and token waste.
Install the minispec CLI, add the minispec skill folder to your project, write a spec in specs/your-feature.md, and instruct Claude to design this to generate the design docs, then implement this to produce code with updated traceability.
High-intent search queries and answers about installing and using this skill.
To create design specs with traceability, use a three-level architecture that separates specs, design, and code into distinct artifacts. This enforces deterministic progression from human specs to design docs and implementation, reducing misalignment and token waste.
You generate design docs and CRC cards from a feature specification by placing your spec in the specs directory and instructing the CLI to design it. This produces structured artifacts including design.md, crc-*.md, sequence files, and UI layouts for design reviews.
The best way to track design phases and task progression is using TaskCreate and TaskUpdate patterns within a CLI workflow. This keeps stakeholders focused and ensures deterministic progression through the design and implementation phases.
Yes, you can use a CLI-driven design review workflow for solo development projects. The framework is built for small to mid-size teams and solo developers, providing modular artifacts and traceability hooks without heavy overhead.
You maintain traceability hooks when implementing code by instructing the framework to implement the design docs. It generates source code in the src directory while automatically updating the traceability links back to the original specs and design artifacts.
Yes, this spec-driven design approach works without external dependencies. The framework operates independently with its own CLI, folder structure, and artifact templates, requiring no additional libraries to generate or maintain design documents.
jaxxstormGuide users through OpenSpec change-cycle workflows in a codebase.
AhmedHassaan-7OSAutomate implementation planning to generate design artifacts from a plan template.
boringdataManage Kurt project sources, targets, and progress via the kurt CLI.
leobessaCodify AI standards, guardrails, audit trails, and policies into organizational governance.
