skills.rest
pko89403
pko89403COMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec

Generate repository-specific design specs at raw/design/specs/ski-NNN-<slug>.md.

1|Updated Apr 8, 2026
Search Tags:#workflow#documentation#spec#software-engineering#spec-driven-development#project-spec
One-click install
npx skills add https://github.com/pko89403/ZeroAlign-Rec --skill spec-pko89403
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/pko89403/ZeroAlign-Rec/tree/main/.agents/skills/spec
Command: npx skills add https://github.com/pko89403/ZeroAlign-Rec --skill spec-pko89403

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This centralizes and accelerates the creation of formal project or feature specs before implementation, ensuring alignment and reducing downstream rework.

Core Features & Use Cases

  • Spec scaffold: generates a repository-scoped spec file to guide design and implementation.
  • Clarification workflow: helps define objectives, acceptance criteria, constraints, and boundaries before coding.
  • Structured delivery: outputs the spec at raw/design/specs/ski-NNN-<slug>.md and provides project-appropriate references and workflow commands.

Quick Start

Type /spec to generate a repository-specific design spec before implementation.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I create a structured software design spec before implementation?▼

To create a structured software design spec, use the /spec command to generate a repository-specific spec file at raw/design/specs/ski-NNN-<slug>.md. This scaffold clarifies objectives, acceptance criteria, constraints, and boundaries before coding begins.

What is spec-driven development and how does it reduce rework?▼

Spec-driven development centralizes formal project or feature specs before implementation to ensure alignment and reduce downstream rework. It clarifies objectives, acceptance criteria, constraints, and boundaries for feature work through a structured specification file.

Can I use spec-driven development with Python tools like pytest and mypy?▼

Yes, spec-driven development supports repo-level Python commands including uv run pytest, uv run ruff check ., uv run mypy src, and uv run sid-reco doctor. These commands are integrated into the generated spec workflow references.

What's the best way to define acceptance criteria and constraints for a feature?▼

The best way to define acceptance criteria and constraints is through a clarification workflow that generates a repository-scoped spec file. This process helps establish boundaries and objectives before implementation, reducing misalignment and rework.

Where should project spec files be stored in a repository?▼

Project spec files should be stored at raw/design/specs/ski-NNN-<slug>.md within the repository. This structured delivery path provides project-appropriate references and workflow commands alongside the specification document.

Related Skills

Explore More Software Engineering Skills→
julianobarbosajulianobarbosa
7

python-project

Scaffold Python projects with uv, ruff, mypy, pytest, and Flask templates.

Community
Intermediate
Row0902Row0902

Verify Project Health

Run uv commands for linting, formatting, and tests to validate project health.

Community
Intermediate
kartikfedkartikfed

python-quality

Run Black, Ruff, Mypy, and Pytest checks on Python code.

Community
Intermediate
EstomEstom

feature-forge

Define structured feature specifications with EARS requirements and Given/When/Then acceptance criteria.

Community
Advanced