skills.rest
Varuas37
Varuas37COMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-workflow

Automate specification-driven development workflows from issue capture to final review.

1|Updated Jan 26, 2026
Search Tags:#workflow#specification#verification#contracts#issue-tracking#design-docs
One-click install
npx skills add https://github.com/Varuas37/spec-test --skill spec-workflow-varuas37
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-workflow
Source: https://github.com/Varuas37/spec-test/tree/main/src/spec_test/skills/spec-workflow
Command: npx skills add https://github.com/Varuas37/spec-test --skill spec-workflow-varuas37

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes and accelerates the creation and verification of software features by guiding teams through a formal specification-driven workflow from idea to verified code.

Core Features & Use Cases

  • Stepwise guidance through Issue, Spec, Implement, Verify, and Review with dedicated skills.
  • Encourages documentation and formal verification to reduce defects and miscommunication.
  • Use Case: A team takes a feature request, converts it into a tracked issue, formal specs, contracts, tests, and a final review before shipping.

Quick Start

  • Create an issue file under design/issues/
  • Define specs under design/specs/
  • Implement with src/ and tests/ using contracts and tests
  • Run spec-test verify
  • Perform a final review with spec-review

Frequently Asked Questions about spec-workflow

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

FAQPage Schema
How do I automate a specification-driven development workflow from issue to verification?▼

A specification-driven workflow standardizes feature creation by guiding teams through issue capture, spec documentation, contract implementation, and test verification. It enforces a structured pipeline to reduce defects and miscommunication before shipping code.

What is the best way to structure design docs and issue tracking for software features?▼

The best way to structure design docs and issue tracking is by creating issue files under design/issues/ and defining formal specs under design/specs/. This enforces metadata-driven documentation and tracks features from initial request to final review.

How do I implement code with contracts and verify through tests in a structured pipeline?▼

To implement code with contracts and verify through tests, you define specifications, write source code and tests in dedicated directories, then run deterministic verification commands. This enforces formal verification and reduces defects across software projects.

Does this specification workflow require specific dependencies or platforms to run?▼

This specification workflow operates with no external dependencies and relies on frontmatter-driven metadata for configuration. It can be applied across software projects without requiring specific platforms or additional environment setup.

When should I use a formal specification-driven workflow instead of informal development?▼

You should use a formal specification-driven workflow when reducing defects and miscommunication is critical for software projects. It enforces stepwise guidance through issue tracking, design docs, and formal verification before shipping features.

Related Skills

Explore More Software Engineering Skills→
cmb-sycmb-sy
1

feature-dev

Coordinate a nine-phase feature development workflow with gates and reviews.

Community
Advanced
Varuas37Varuas37
1

spec-verify

Verify specifications against test results using the spec-test tool.

Community
Intermediate
pradyumnasagarpradyumnasagar
6

agent-handoff

Automate inter-skill data transfer and provenance capture via JSON Material Passports.

Community
Advanced
c-sonnierc-sonnier
2

convergence-implement

Automate phase-based feature implementation with test-first verification checkpoints.

Community
Advanced