archflow

Orchestrates phase-based software development with specialized agents, releases, and approval gates.

28|4|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/AZidan/archflow --skill archflow-azidan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archflow
Source: https://github.com/AZidan/archflow/tree/main/plugin/skills/archflow
Command: npx skills add https://github.com/AZidan/archflow --skill archflow-azidan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI coding sessions lose context between runs, frontend and backend drift apart, and nobody can say what is actually finished. Archflow structures AI-assisted development into explicit lifecycle phases with file-based handoffs, so project state survives sessions and agents work from shared contracts instead of chat history. ## Core Features & Use Cases - Phase-based lifecycle management: Guides projects through strategy, design, API architecture, implementation, quality, launch, and enhancement phases, each with its own instruction file and approval gate. - Release and backlog management: Tracks stories across roadmap, release, backlog, and history YAML files with a readiness pipeline from backlog stub to shipped release. - Specialized agent orchestration: Dispatches domain agents (product-strategist, ux-designer, api-contract-architect, ui-engineer, qa-engineer, and others) that communicate through repository artifacts rather than messages. - Design system and API contract enforcement: Requires every UI-producing agent to follow the project's chosen design system file and binds frontend and backend work to a single API contract. - Use Case: A developer with an existing codebase runs /archflow:onboard to audit the stack and import context, then uses /archflow:release and /archflow:feature to plan and build stories one at a time, with QA and acceptance review before anything merges. ## Quick Start Ask the agent to run /archflow:status to see where the project stands and what to do next, or /archflow:init to set up a new project.

Frequently Asked Questions about archflow

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

FAQPage Schema
How do I set up Archflow in an existing codebase?

Run /archflow:onboard to audit the repository, detect the stack from manifests and lockfiles, import existing context, and pick the appropriate starting phase. It creates the .archflow directory with instructions, phase files, and schemas without assuming a greenfield project.

What is the difference between quick mode and full mode in Archflow?

Quick mode runs a single implicit release with gates that record but do not block, suited for solo projects. Full mode provides an explicit release pipeline with enforced advisory gates and role lanes for teams. Switch between them with /archflow:mode; both use the same schema.

Which AI coding agents and hosts does Archflow support?

Archflow runs on Claude Code, OpenAI Codex, GitHub Copilot CLI, Cursor, Gemini CLI, and OpenCode from the same files in the repository. It also connects to external tools like Jira, Notion, Linear, GitHub, Slack, and Trello via MCP servers configured with /archflow:setup-mcp.

How does Archflow keep frontend and backend implementations consistent?

An api-contract-architect agent produces a single API contract that binds both ui-engineer and api-engineer with zero tolerance for deviation. The qa-engineer verifies implementations against the contract, and its location is resolved through api_contract_path in project-settings.yaml.

Can Archflow run stories unattended overnight?

Yes, /archflow:autopilot runs queued stories on a single branch after an upfront interview that pre-authorizes review gates. It never merges to main, parks stories with undecided questions, and records all decisions in a durable run ledger under .archflow/autopilot/.

What happens when a design system file is missing in an Archflow project?

Agents stop and ask rather than guessing. On any project with a UI, a missing design system triggers /archflow:design to pick one before any UI work proceeds, since component vocabulary in wireframes and handoffs must come from the chosen system's file.