spec

Enforce disciplined specification workflows with testable acceptance criteria across design phases.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/jivebreaddev/skills-claude-agent --skill spec-jivebreaddev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/jivebreaddev/skills-claude-agent/tree/main/.claude/skills/spec
Command: npx skills add https://github.com/jivebreaddev/skills-claude-agent --skill spec-jivebreaddev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a rigorous, step-by-step specification process that prevents vague or untestable requirements, ensuring every design phase is properly documented, reviewed, and archived.

Core Features & Use Cases

  • Enforces the Iron Law, Red Flags, and Phase Completion Protocol to prevent skipped checkpoints.
  • Requires explicit acceptance criteria and documented trade-offs, with mandatory records for wrap-up analysis.
  • Supports long-context sessions, multi-AI reviews, and formal wrap-up workflows, with context preservation.

Quick Start

Run the spec skill to establish testable acceptance criteria and formal checkpoints for your project.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I enforce testable acceptance criteria in my software specification workflow?

To prevent skipping steps in your specification workflow, apply a phase completion protocol that enforces mandatory checkpoints and requires explicit justification for any deviations. This ensures traceable decisions are maintained from Phase 1 through Wrap-up without undocumented gaps.

How do I maintain context preservation during long-context specification sessions?

To maintain context preservation during long-context specification sessions, use a workflow that supports mandatory record-keeping and multi-AI reviews. This ensures traceable decisions and documented trade-offs are preserved across all design phases without losing context.

What is the best way to document design phase trade-offs for wrap-up analysis?

The best way to document design phase trade-offs for wrap-up analysis is to enforce mandatory records at every checkpoint. This requires explicit acceptance criteria and documented decisions across all design areas, creating a traceable archive for formal wrap-up workflows.

Can I use multi-AI reviews for specification checkpoints across different design areas?

Yes, you can use multi-AI reviews for specification checkpoints across different design areas. The specification workflow supports multi-AI reviews alongside long-context sessions, ensuring traceable decisions and mandatory record-keeping are maintained throughout all phases.

Why does my specification workflow need a phase completion protocol?

Your specification workflow needs a phase completion protocol to prevent skipping checkpoints without justification and to eliminate vague or untestable requirements. It enforces the Iron Law and Red Flags, ensuring every design phase is properly documented, reviewed, and archived.