workflow

Orchestrates an ordered sequence of development skills from brainstorming through branch completion.

Updated May 21, 2026
One-click install
npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill workflow-cagesthrottleus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow
Source: https://github.com/CagesThrottleUs/private-ai-harness/tree/main/skills/workflow
Command: npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill workflow-cagesthrottleus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature work often skips critical steps like requirements capture, design review, or documentation, leading to rework and untraceable decisions. This Skill enforces a mandatory, ordered development workflow so every change moves through brainstorming, specification, planning, implementation, review, and branch completion with the right gates in between. ## Core Features & Use Cases - Complexity Assessment: Classifies each change as Trivial, Small, Medium, Large, or Critical and suggests which workflow steps can be safely skipped, always confirming with the user first. - Ordered Skill Pipeline: Sequences skills from research and business-context-intake through brainstorming, spec quality gates, HLD, worktrees, CI setup, planning, TDD implementation, code review, and branch finishing. - Documentation Discipline: Defines artifact locations under .ai/ and wiki/, enforces a wiki sync rule requiring documentation updates in the same commit as behavior changes, and keeps AGENTS.md and CLAUDE.md current. - Use Case: When asked to add a new API endpoint, the Skill routes the work through spec writing, plan creation, test-driven implementation, and code review before allowing a merge. ## Quick Start Invoke the workflow skill and describe the feature or fix you want to build so it can classify the change and run the appropriate sequence of steps.

Frequently Asked Questions about workflow

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

FAQPage Schema
How do I enforce a structured development workflow for AI coding agents?

Invoke the workflow skill before starting any feature or fix. It classifies the change by complexity, then sequences skills for brainstorming, specification, planning, TDD implementation, code review, and branch completion as mandatory gates.

What steps can be skipped for small code changes?

Trivial changes like bug fixes or config updates can skip business-context-intake, high-level-design, api-contract-first, load-testing, and deployment-workflow. The skill always confirms proposed skips with the user before proceeding.

Where does the workflow store specs and design documents?

Ephemeral artifacts go in .ai/YYYY-MM-DD-<feature-slug>/ with subfolders for specs, plans, hld, and reports. Living documentation like API references, ADRs, and changelogs lives in wiki/ and updates in the same commit as behavior changes.

Does the workflow require test-driven development?

Yes, the test-driven-development step activates during implementation and enforces RED-GREEN-REFACTOR: write a failing test, watch it fail, write minimal code, watch it pass, then commit. Code written before tests is deleted.

When should I not use the full workflow?

Skip the full suite for trivial changes like typo fixes, version bumps, or documentation edits. The complexity assessment table maps change signals to suggested skips, but every skip requires explicit user confirmation first.