skills.rest
ormastes
ormastesCOMMUNITY
Explore all skills by this author →
GitHub

SStack Phase Definitions

Define an eight-phase workflow converting tasks into code with acceptance criteria.

Updated May 27, 2026
Search Tags:#verification#acceptance criteria#code implementation#test-first#phase workflow#state file#sstack
One-click install
npx skills add https://github.com/ormastes/Spipe --skill sstack-phase-definitions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: SStack Phase Definitions
Source: https://github.com/ormastes/Spipe/tree/main/doc/00_llm_process/skill_command/skills/claude/lib/sstack_phases
Command: npx skills add https://github.com/ormastes/Spipe --skill sstack-phase-definitions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a complete, phase-by-phase operating procedure for turning a user task into implemented code using a structured SStack workflow with explicit entry/exit criteria and quality gates.

Core Features & Use Cases

  • 8 explicit phases (Dev → Ship) with defined roles, focus, and context budgets to guide the orchestrator workflow.
  • State-file driven execution with gate checks that validate phase exit criteria (e.g., refined goals, acceptance criteria, module lists, and verification evidence).
  • Test-first spec enforcement by requiring failing specs in the Spec phase and a green pass in Verify/Ship.

Quick Start

Use this SStack phase definition reference to run an end-to-end development cycle where each phase writes and validates its portion of the shared state file.

Frequently Asked Questions about SStack Phase Definitions

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

FAQPage Schema
How do I coordinate a test-first build pipeline with explicit phase entry and exit criteria?▼

A test-first build pipeline requires a structured eight-phase workflow that defines specific roles, context budgets, and state-file driven quality gates to validate phase exit criteria from development through shipping.

What is the best way to enforce acceptance criteria during code implementation?▼

Enforcing acceptance criteria requires orchestrator-enforced quality gates that validate phase exit criteria, requiring failing specs during the spec phase and a green pass during verification and shipping.

How does state-file driven execution work for phase workflow coordination?▼

State-file driven execution uses a shared state file where each phase writes and validates its portion, enabling the orchestrator workflow to check gate criteria like refined goals and module lists before proceeding.

Can I apply an 8-phase workflow to bug fixes and code-quality improvements?▼

Yes, the eight-phase workflow applies to feature development, bug fixes, TODO follow-ups, and code-quality improvements by converting a user task into implemented code with measurable acceptance criteria.

Do I need an orchestrator to manage the phase workflow for test-first spec creation?▼

Yes, an orchestrator is required to manage the phase workflow, enforce quality gates, and validate state-file communication to ensure test-first spec creation through verification and shipping.

Related Skills

Explore More Software Engineering Skills→
cdrgurucdrguru
1

gemini-cli-init

Initialize Gemini CLI configuration and auditor persona for the PACK workflow.

Community
Intermediate
elophantoelophanto
116

verification-before-completion

Execute verification commands and report pass/fail with evidence before completion.

Community
Advanced
ste-bahste-bah
7

ci-gate-walker

Run the repository CI gate script and summarize pass or fail results.

Community
Intermediate
NoobyGainsNoobyGains
78

task-planning

Generate step-by-step implementation plans with file paths, code snippets, and test commands.

Community
Advanced