archflow-mode

Shows or switches the Archflow ceremony mode between quick and full.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams and solo developers need different levels of process ceremony, and switching between a lightweight solo workflow and a full team pipeline usually means rewriting project configuration. This Skill shows or switches the Archflow ceremony mode in place, without rewriting any project data. ## Core Features & Use Cases - Show Current Mode: Reads the mode from .archflow/roadmap.yaml and explains what it means for releases, gates, and roles. - Switch Modes In Place: Moves between quick (solo, auto-satisfied gates) and full (team, enforced advisory-recorded gates) with no data loss, since both modes share the same v2.0 schema. - Smart Graduation Prompt: Detects growth signals such as a second release, a second contributor, or project size thresholds, and offers an upgrade to full mode without forcing it. - Use Case: A solo developer whose side project gains a collaborator runs the mode switch to full, which materializes release files, enables readiness gates, and optionally turns on code review for every story. ## Quick Start Ask the agent to run /archflow-mode full to switch the project from quick mode to full team ceremony.

Frequently Asked Questions about archflow-mode

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

FAQPage Schema
How do I switch Archflow from quick mode to full mode?

Run /archflow-mode full. The switch updates mode in .archflow/roadmap.yaml and current-phase.yaml, ensures release and backlog files exist, turns readiness gates on as advisory-recorded, and commits the change without rewriting existing data.

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

Quick mode uses one implicit release, auto-satisfied gates, and a single solo lane. Full mode adds an explicit release pipeline, backlog stubs with promotion, enforced advisory-recorded gates, per-phase approvals, and PM, designer, architect, engineer, and QA roles.

Does switching Archflow mode delete or rewrite project data?

No. Both modes share the same v2.0 schema, so switching is an in-place change. Moving from full to quick leaves release files and history intact, and moving from quick to full only materializes ceremony files.

When does Archflow suggest upgrading from quick to full mode?

The framework offers an upgrade when a quick project requests a second release, gains a second contributor, or crosses a size threshold in story count, file count, or repo age. It only offers the switch and remembers a decline.

Does changing the mode automatically enable code review agents?

No. Switching modes does not silently rewrite the optional_agents block in project-settings.yaml. The Skill presents current review settings and asks whether to turn code review or accessibility review on or off.