agent-framework-cli
v2.2.2
Published
Turn GitHub Copilot into a coordinated engineering team — specification-driven development lifecycle with quality gates, persistent memory, and human-in-the-loop governance
Maintainers
Readme
Agent Framework CLI
Supercharge your agentic development — stop fiddling with agent config and start shipping.
agent-framework-cli sets up everything you need to follow a perfect SDLC lifecycle with GitHub Copilot, in one command. Spec → Plan → Implement → Review → Ship, with quality gates and persistent memory baked in.
One command. Full setup.
npm install -g agent-framework-cli
acli setupThat's it. acli setup asks you two quick questions, installs all dependencies, and scaffolds your project. Open Copilot Chat and go:
/acli.run Build a user authentication system with OAuth supportThe Power Stack
Agent Framework wires together four best-in-class tools so you don't have to:
| Tool | What it does for you | |------|----------------------| | spec-kit | Spec-driven development engine — keeps every feature grounded in structured requirements, not vibes | | Fleet | Multi-agent orchestration — runs architect, security, dev, and QA agents in the right order with the right context | | Superpowers Bridge | Connects Copilot to brainstorming, TDD enforcement, and structured code review workflows | | Beads (optional) | Semantic memory across sessions — your architecture decisions, ADRs, and task state survive every conversation |
Choose Git-based memory (zero extra tooling, context in plain files) or Beads-based memory (advanced semantic search + chunking).
acli setupasks you at install time.
Why bother?
AI coding assistants write code fast but without discipline. Left unchecked:
- Features get built from vague prompts instead of structured specs
- Architecture drifts because every session starts fresh
- Tests get skipped, security gets overlooked, reviews get bypassed
- Nobody knows why a decision was made two weeks ago
Agent Framework wraps Copilot in a governed engineering workflow — spec before code, review before merge, memory that persists.
The Lifecycle
Specify → Clarify → Plan → Checklist → Tasks
│
🚦 Human Gate
│
Finish ← Verify ← Implement ← Review ← Analyze
│ │
🚦 Human Gate 🚦 Human GateRun /acli.run <feature> and the orchestrator drives the whole thing. You only touch it at the three approval gates.
5 Agents, 1 Team
| Agent | Job |
|-------|-----|
| orchestrator | Routes work, enforces gates, runs tasks in parallel |
| architect | Writes specs, plans, ADRs — tech-agnostic and rigorous |
| security | OWASP checklists, threat modeling, vulnerability review |
| development | TDD implementation, plan-conformant, hands off cleanly |
| qa | Code review, test coverage, acceptance validation |
Slash Commands
Everyday:
| Command | What it does |
|---------|-------------|
| /acli.run <feature> | Full lifecycle start to finish |
| /acli.onboard | Analyse and bootstrap an existing codebase |
| /acli.implement | Jump straight to implementation |
Spec & Planning:
| Command | What it does |
|---------|-------------|
| /acli.constitution | Define your project principles & architecture boundaries |
| /acli.specify | Author a structured feature spec with acceptance criteria |
| /acli.plan | Generate implementation plan + architecture decision records |
| /acli.tasks | Break the plan into prioritised, dependency-ordered tasks |
| /acli.checklist | Generate security, a11y, and performance quality gates |
Review & Ship:
| Command | What it does |
|---------|-------------|
| /acli.critique | Spec-aligned code review with severity ratings |
| /acli.debug | Structured root-cause analysis |
| /acli.finish | Branch cleanup and merge readiness check |
Brownfield? No problem.
/acli.onboard auto-scans your existing codebase, generates a tailored constitution + reference architecture, and gets you into the lifecycle without starting from scratch.
Workspace Layout
.github/
agents/ ← agent definitions
skills/ ← reusable skills
prompts/ ← slash commands
.specify/
memory/ ← constitution, architecture, quality standards
specs/ ← specs, plans, checklists, tasks
.beads/ ← persistent memory (if beads-based memory selected)CLI Reference
| Command | Description |
|---------|-------------|
| acli setup [--check] | Install dependencies + scaffold project (interactive) |
| acli install <agent> | Install a specific agent |
| acli remove <agent> | Remove an installed agent |
| acli list agents\|skills | List available agents or skills |
| acli update [agent] | Update agents, prompts, and skills |
| acli config | View or modify framework configuration |
Requirements
- Node.js >= 18
- VS Code + GitHub Copilot Chat
- Python >= 3.8 (for spec-kit)
Contributing
See CONTRIBUTING.md. MIT licensed.
