skills.rest
LucasBiason
LucasBiasonCOMMUNITY
Explore all skills by this author →
GitHub

spec-driven-core

Generate specification artifacts from text, documents, code, or diagrams.

Updated Aug 23, 2026
Search Tags:#planning#documentation#specification#requirements#traceability#design-tradeoffs
One-click install
npx skills add https://github.com/LucasBiason/engineering-knowledge-base --skill spec-driven-core
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-core
Source: https://github.com/LucasBiason/engineering-knowledge-base/tree/main/.claude/skills/workflow/spec-driven-core
Command: npx skills add https://github.com/LucasBiason/engineering-knowledge-base --skill spec-driven-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec Driven Core provides a universal, repeatable process to transform any input—text, documents, code, diagrams, or conversations—into a complete specification set. It enables teams to move from vague ideas to structured, testable artifacts without diving into implementation prematurely.

Core Features & Use Cases

  • Phase-driven workflow from input analysis to design translation, delivering artifacts such as system-context.md, problem-statement.md, glossary.md, prd.md, functional-requirements.md, acceptance-criteria.md, non-functional-requirements.md, architecture.md, data-model.md, ADRs, and open-questions.md.
  • Automatic traceability and documentation generation to support reviewer sign-off and onboarding.
  • Use cases include starting a new project, clarifying feature scope, documenting backlog items, and aligning stakeholders before implementation.

Quick Start

Enter Plan mode and provide your initial input to start generating the complete specification suite.

Frequently Asked Questions about spec-driven-core

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn vague inputs into structured software specifications?▼

Documenting technical plans requires generating a complete specification suite including problem-statement.md, functional-requirements.md, and ADRs. This extracts requirements and captures design tradeoffs to align stakeholders before any implementation begins.

What is the best way to extract functional requirements from existing code or diagrams?▼

Generating acceptance criteria happens during the requirements extraction and design translation phases. It transforms initial inputs into non-functional requirements and detailed specifications, ensuring the resulting artifacts support reviewer sign-off and project onboarding.

Can I use this specification workflow for improving existing systems?▼

Yes, you can use this specification workflow for improving existing systems by applying it to document backlog items and clarify feature scope. It transforms current technical context into updated requirement artifacts and architecture documents without premature implementation.

Do I need to enter Plan mode to generate a complete specification set?▼

Architecture decision records are generated during the design translation phase. This phase evaluates technical plans and documents design tradeoffs within the architecture.md file, providing clear rationale for structural choices and capturing open questions for stakeholder alignment.

Related Skills

Explore More Software Engineering Skills→
dtsongdtsong
1

intake-skill

Transform natural language project descriptions into structured engagement briefs.

Community
Advanced
cicero78Mcicero78M

speckit-plan

Generate data-model.md, contracts/, and quickstart.md from plan templates.

Community
Intermediate
popo0407popo0407

git-versioning

Standardizes GitHub version control with Git Flow and Conventional Commits.

Community
Intermediate
ajayjoshi-ciphersonicajayjoshi-ciphersonic

plan

Create structured Markdown project plans without modifying existing files.

Community
Basic