workflow

Route software delivery work through brief, spec, tdd, code, review, and draft-pr stages.

51|2|Updated Apr 20, 2026

Search Tags:#automation #workflow #orchestration #phases #development-process #ai-assisted

Ready to run

npx skills add https://github.com/g2i-ai/agents --skill workflow-g2i-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow
Source: https://github.com/g2i-ai/agents/tree/main/skills/workflow
Command: npx skills add https://github.com/g2i-ai/agents --skill workflow-g2i-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating the end-to-end software delivery workflow by routing work through the brief, spec, tdd, code, review, and draft-pr stages to minimize manual coordination.

Core Features & Use Cases

Orchestrates the standard delivery flow across brief, spec, tdd, code, review, and draft-pr
Routes work to the appropriate stage skills and supports partial runs (e.g., spec -> code) or resuming from existing artifacts
Provides after-action summaries and tracks artifact paths (docs/briefs/, docs/specs/, docs/qa/reports/)
Keeps the workspace synchronized with stage outputs and enforces a clean handoff between steps

Quick Start

Ask this skill to run the full workflow from brief to draft-pr or to execute a partial sequence like spec -> code for a given feature.

Frequently Asked Questions about workflow

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

FAQPage Schema

How do I orchestrate an end-to-end software delivery workflow from feature brief to pull request?▼

Software delivery workflow orchestration routes work sequentially through brief, spec, tdd, code, review, and draft-pr stages, minimizing manual coordination by automating stage invocation and guided handoffs between skills.

Can I run a partial development workflow or resume from an existing spec artifact?▼

Yes, workflow orchestration supports partial executions like spec to code and can resume from existing artifacts, checking outputs in docs/briefs, docs/specs, and docs/qa/reports to synchronize the workspace.

What is the standard software delivery process for AI-assisted feature development?▼

The AI-assisted development process coordinates work across six stages: brief, spec, tdd, code, review, and draft-pr. It maintains artifact visibility and enforces clean handoffs between each stage skill.

Does the workflow orchestration skill support tracking outputs like briefs and QA reports?▼

Yes, workflow orchestration tracks artifact paths across docs/briefs, docs/specs, and docs/qa/reports, providing after-action summaries and keeping the workspace synchronized with stage outputs.

What's the best way to automate stage transitions in a test-driven development workflow?▼

Automating stage transitions is handled by orchestration logic that invokes stage skills sequentially from brief to draft-pr, enforcing clean handoffs and synchronizing the workspace with TDD and code review outputs.