skills.rest
jcg-admin
jcg-adminCOMMUNITY
Explore all skills by this author →
GitHub

workflow-structure

Generates requirements specifications and design documents with Given/When/Then acceptance criteria for Phase 7.

Updated Mar 14, 2026
Search Tags:#acceptance criteria#design document#spec-driven development#quality checklist#given when then#workflow phase#requirements specification
One-click install
npx skills add https://github.com/jcg-admin/IACT-ui --skill workflow-structure-jcg-admin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-structure
Source: https://github.com/jcg-admin/IACT-ui/tree/main/.claude/skills/workflow-structure
Command: npx skills add https://github.com/jcg-admin/IACT-ui --skill workflow-structure-jcg-admin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? It removes ambiguity before task decomposition by producing a formal requirements specification (and optionally a technical design document) for the active work package, ensuring every requirement has testable acceptance criteria before implementation begins. ## Core Features & Use Cases - Requirements Specification: Creates a named requirements-spec.md from a template with user stories and Given/When/Then acceptance criteria, mapped to the approved plan. - Complexity-Based Design Docs: For work packages with 10+ estimated tasks, additionally generates a design.md covering architectural decisions, affected components, data flows (Mermaid diagrams), rollback plans, and testing. - Quality Gate Enforcement: Requires a 20-item spec-quality checklist at 100% with zero unresolved [NEEDS CLARIFICATION] markers, plus explicit human approval before advancing to Phase 8 decomposition. - Use Case: After a plan is approved in Phase 6, run this skill to produce 'skill-activation-requirements-spec.md' and its checklist, present the spec for human sign-off, then proceed to task decomposition. ## Quick Start Ask the assistant to start Phase 7 DESIGN/SPECIFY for the active work package and produce the requirements specification with acceptance criteria.

Frequently Asked Questions about workflow-structure

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

FAQPage Schema
How do I write a requirements specification with Given/When/Then acceptance criteria?▼

Use the requirements-specification template to map each approved requirement to a SPEC entry containing a description, technical considerations, and acceptance criteria written as Given/When/Then blocks. Each criterion must be objectively verifiable before the spec can pass the quality checklist.

When do I need a design document in addition to a requirements spec?▼

A design.md is required when the work package is estimated at 10 or more tasks. It documents architectural decisions, affected components, Mermaid data-flow diagrams, dependencies, rollback plans, and test cases, complementing the requirements spec that defines what to build.

What is spec-driven development and when should I use it?▼

Spec-driven development is a four-phase methodology (Requirements, Design, Tasks, Implementation) for complex work. Use it when work exceeds two hours, affects architecture, spans multiple components, or carries regression risk; skip it for trivial single-file changes.

Can I proceed to task decomposition with unresolved NEEDS CLARIFICATION markers?▼

No. The gate from specification to decomposition requires zero unresolved [NEEDS CLARIFICATION] markers and a 100% complete spec-quality checklist. Items that still fail after two iterations need explicit user approval before continuing.

Why must diagrams use Mermaid instead of ASCII art in specs?▼

The skill mandates Mermaid for all flows, models, and diagrams so they render consistently in Markdown viewers and documentation pipelines. Sequence diagrams are used for flows with three or more participants, and flowcharts for branching alternative flows.

Related Skills

Explore More Software Engineering Skills→
jcg-adminjcg-admin

workflow-scope

Define explicit in-scope and out-of-scope boundaries for work packages in Phase 6 planning.

Community
Intermediate
friedbotstudiofriedbotstudio
5

swarm-plan

Decompose an approved specification into a dependency-ordered swarm plan.

Official
Advanced
CygnusfearCygnusfear
5

check-plan

Audit implementation progress against a plan and generate per-file TODOs.

Community
Basic
nevesbnevesb

quick-design

Draft lightweight design specs for small gameplay changes with acceptance criteria.

Community
Intermediate