archflow
/archflow
Zarządza fazowym procesem Archflow od strategii i projektu przez implementację i QA po start, wraz z roadmapami, wydaniami, gałęziami funkcji, orkiestracją agentów i konfiguracją MCP.
- Autor
- AZidan ↗
- Repozytorium
- archflow ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 27.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 76
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Zarządza fazowym procesem Archflow od strategii i projektu przez implementację i QA po start, wraz z roadmapami, wydaniami, gałęziami funkcji, orkiestracją agentów i konfiguracją MCP.
Oryginalny opis (EN)
Phase-based development workflow manager that guides projects through structured phases from strategy and design through implementation, quality assurance, and launch. Manages roadmaps, releases, feature branches, agent orchestration, and MCP server configuration. Load when the user talks about Archflow phases, releases, the backlog, or asks what to do next in an Archflow project.
Jak działa
- Commands
- Framework files (shipped with the plugin)
- When this skill is invoked directly
- Working in an Archflow project
Podgląd SKILL.md
---
name: archflow
description: Phase-based development workflow manager that guides projects through structured phases from strategy and design through implementation, quality assurance, and launch. Manages roadmaps, releases, feature branches, agent orchestration, and MCP server configuration. Load when the user talks about Archflow phases, releases, the backlog, or asks what to do next in an Archflow project.
---
# Archflow — Phase-Based Development Workflow
`.archflow/instructions.md` is the always-loaded core. `.archflow/reference.md` holds the detail and is read on demand.
Archflow manages the full software development lifecycle through structured phases, from onboarding
existing codebases to launching production software. Releases are the outer loop (schema v2.0);
phases are the inner loop.
## Commands
Every Archflow action is a namespaced slash command — there is no argument-style `/archflow <sub>`.
```
/archflow-status → Where the project stands: phase, mode, active release, what's next
/archflow-help [command] → Every command with a one-line usage note, and how Archflow works
/archflow-init → Set up a NEW, empty project (creates .archflow/, Phase 1)
/archflow-onboard → Set up an EXISTING codebase (audit, import context, pick phase)
/archflow-migrate → Upgrade a v1.0 archflow-onboarded project (sprints) → v2.0 (releases); dry-run then apply
/archflow-mode [quick|full] → Show/switch ceremony mode: quick (solo) or full (team)
/archflow-release [new|start|ship] → Release pipeline: status, cut, start building, ship
/archflow-setup-mcp [tool] → Connect an external tool via MCP (Jira, Notion, Linear, ...)
/archflow-groom [story-id] → Detail or refine a story (backlog stub, or in-release)
/archflow-feature [name/description|story-id] → Add a story, or pull one into the active release
/archflow-autopilot [story-id ...] → Run queued stories unattended on one branch (interview, then silent)
/archflow-design [pick|list|name] → Show or change the project's design system (once per project)
/archflow-contract [story-id] → Contract architecture, or one story's endpoints
/archflow-issue [story-id|defer ...] → Record a defect on a story in the active release, or defer a minor one
/archflow-doctor [--validate|--fix] → Environment + project health check; --fix repairs upgrade drift
/archflow-studio [stop|status|port n] → Local web workspace over the same files; onboards and migrates from the UI (beta)
/archflow-telemetry [on|off|status] → Show or change anonymous usage telemetry (on by default)
```
Command bodies live in `.opencode/commands/archflow-<name>.md`. When you need to run one from
inside another flow (e.g. onboarding calls setup-mcp), read that file and follow it inline.
## Framework files (shipped with the plugin)
- `.opencode/archflow/skills/archflow/instructions.md` — agent-neutral base instructions
- `.opencode/archflow/skills/archflow/phases/` — per-phase instruction files
- `.opencode/archflow/skills/archflow/schemas/` — roadmap / release / backlog / history schemas
- `.opencode/archflow/skills/archflow/workflow.md` — git branching strategy
- `.opencode/archflow/skills/archflow/base-dsl-structure.yaml` — DSL template for design artifacts
- `.opencode/archflow/skills/archflow/mcp-registry.yaml` — curated MCP server registry
- `.opencode/archflow/skills/archflow/design-systems/` — design-system reference files, one plain
markdown file per system (not skills, not commands — loaded by explicit path only)
- `.opencode/archflow/scripts/migrate.py` — v1.0 → v2.0 migration engine
`init` / `onboard` copy `instructions.md`, `phases/`, `schemas/`, `design-systems/`, and
`workflow.md` into the project's `.archflow/`. Paths beginning with `.archflow/` are always
**project-local**.
## When this skill is invoked directly
If the user runs this skill on its own (`/archflow-archflow`), behave exactly like
`/archflow-status`: read and follow `.opencode/commands/archflow-status.md`.
## Working in an Archflow project
1. Read `.archflow/current-phase.yaml` → `phase_file`, then follow
`.archflow/phases/phase-{current}-{name}.md`.
2. **Before producing or reviewing any UI**, read `.archflow/design-system.yaml`, then read and
follow `.archflow/design-systems/{design_system}.md`. Component names in wireframes, DSL files
and handoffs come from its vocabulary table. If the file is missing on a project with a UI,
stop and run `/archflow-design`.
3. `.archflow/instructions.md` (loaded by the SessionStart hook) is the source of truth for agents
per phase, the release model, and the critical rules — do not restate it here.
4. Stop for explicit user approval at every phase gate.
Pliki w paczce (76)
- SKILL.md 5 KB
- base-dsl-structure.yaml 9 KB
- instructions.md 5 KB
- mcp-registry.yaml 3 KB
- reference.md 16 KB
- stack-detection.md 4 KB
- test-accounts.example.yaml 1 KB
- workflow.md 7 KB
- design-systems/CONTRIBUTING.md 7 KB
- design-systems/custom-tokens.md 12 KB
- design-systems/fluent2.md 9 KB
- design-systems/liquid-glass.md 9 KB
- design-systems/material3.md 8 KB
- design-systems/shadcn.md 8 KB
- design-systems/examples/custom-tokens/detail.html 9 KB
- design-systems/examples/custom-tokens/detail.png 256 KB
- design-systems/examples/custom-tokens/list.html 10 KB
- design-systems/examples/custom-tokens/list.png 252 KB
- design-systems/examples/custom-tokens/login.html 4 KB
- design-systems/examples/custom-tokens/login.png 139 KB
- design-systems/examples/custom-tokens/theme.css 8 KB
- design-systems/examples/fluent2/detail.html 9 KB
- design-systems/examples/fluent2/detail.png 232 KB
- design-systems/examples/fluent2/list.html 11 KB
- design-systems/examples/fluent2/list.png 239 KB
- design-systems/examples/fluent2/login.html 3 KB
- design-systems/examples/fluent2/login.png 394 KB
- design-systems/examples/fluent2/theme.css 6 KB
- design-systems/examples/liquid-glass/detail.html 3 KB
- design-systems/examples/liquid-glass/detail.png 500 KB
- design-systems/examples/liquid-glass/list.html 5 KB
- design-systems/examples/liquid-glass/list.png 480 KB
- design-systems/examples/liquid-glass/login.html 2 KB
- design-systems/examples/liquid-glass/login.png 565 KB
- design-systems/examples/liquid-glass/theme.css 5 KB
- design-systems/examples/material3/detail.html 3 KB
- design-systems/examples/material3/detail.png 114 KB
- design-systems/examples/material3/list.html 4 KB
- design-systems/examples/material3/list.png 133 KB
- design-systems/examples/material3/login.html 2 KB
- design-systems/examples/material3/login.png 71 KB
- design-systems/examples/material3/theme.css 6 KB
- design-systems/examples/shadcn/detail.html 9 KB
- design-systems/examples/shadcn/detail.png 233 KB
- design-systems/examples/shadcn/list.html 10 KB
- design-systems/examples/shadcn/list.png 240 KB
- design-systems/examples/shadcn/login.html 3 KB
- design-systems/examples/shadcn/login.png 79 KB
- design-systems/examples/shadcn/theme.css 5 KB
- phases/phase-1-strategy.md 4 KB
- phases/phase-2-design.md 7 KB
- phases/phase-2.25-hifi-design.md 6 KB
- phases/phase-2.5-api-architecture.md 5 KB
- phases/phase-3-implementation.md 21 KB
- phases/phase-4-quality.md 9 KB
- phases/phase-5-launch.md 6 KB
- phases/phase-6-enhancement.md 6 KB
- phases/phase-onboarding.md 11 KB
- phases/phase-setup.md 8 KB
- phases/onboarding/agent-prompts.md 14 KB
- phases/onboarding/audit.md 10 KB
- phases/onboarding/finalize.md 6 KB
- phases/onboarding/synthesis.md 9 KB
- schemas/autopilot-schema.yaml 12 KB
- schemas/backlog-schema.yaml 5 KB
- schemas/current-phase-schema.yaml 3 KB
- schemas/history-schema.yaml 3 KB
- schemas/project-settings-schema.yaml 7 KB
- schemas/release-schema.yaml 15 KB
- schemas/roadmap-schema.yaml 7 KB
- stacks/README.md 1 KB
- stacks/express-mongo-next.yaml 1 KB
- stacks/fastapi-postgres-react.yaml 1 KB
- stacks/native-mobile.yaml 1 KB
- stacks/nestjs-postgres-react.yaml 1 KB
- stacks/react-native-mobile.yaml 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · AZidan/archflow | 100 | MIT |
| AZidan/archflow | 100 | MIT |
| AZidan/archflow | 100 | MIT |
| AZidan/archflow | 100 | MIT |
| AZidan/archflow | 100 | MIT |
| AZidan/archflow | 100 | MIT |
| AZidan/archflow | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 948d8221461c (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100archflow-init
Konfiguruje Archflow w nowym, pustym projekcie: tworzy katalog .archflow/ i rozpoczyna od fazy 1. - 100archflow-init
Konfiguruje Archflow w nowym, pustym projekcie: tworzy katalog .archflow/ i rozpoczyna od fazy 1.