Skip to main content
Asterweave

Asterweave

Reusable agentic software delivery for Claude Code.

Define the goal. Asterweave understands the repository, coordinates specialized agents, implements the change, verifies it, and drives delivery to a pull request — pausing for your approval at the decisions that are still yours to make.

Get startedArchitectureCommandsGitHub

How it fits together

One deterministic graph connects a goal to a verified pull request.

Developer
↓
Asterweave
↓
Repository context
↓
Specs
↓
Agents + skills
↓
Verification
↓
PR / CI

What Asterweave is

Not full autonomy where human approval is still required — deliberate, verifiable delivery.

Repository-aware

Discovers and preserves the architecture already in your repository instead of imposing one.

Spec-driven

Reads and links to specs/ when one exists, with proportional rigor for the size of the change.

Agentic

Thirteen narrowly scoped specialists, least-privilege by design, delegated bounded work per graph node.

Resumable

Durable workflow state and an append-only event ledger — a new session picks up exactly where the last one stopped.

Verification-first

A passing unit test is context, not proof. Runtime acceptance evidence is independent and required.

Safe automation

Pauses for human approval after planning and before push/PR; never merges, self-approves, or force-pushes.

Extensible

A repository can route stages to project-specific agents and add quality gates — never remove a mandatory one.

Get started in two commands

Align the repository once, then deliver work items whenever you have one.

1. Align your repository

/asterweave:scaffold

Reads your code, tests, and CI, then proposes an evidence-backed CLAUDE.md, .claude/rules/, and .claude/asterweave.json for your approval.

2. Deliver a work item

/asterweave:deliver owner/repository#123

Analyzes, plans, implements, tests, verifies, reviews, and opens a pull request — pausing for your approval before push/PR unless invoked with --auto-pr.

Daily workflowCommand referenceArchitecture

What is Asterweave?​

Asterweave is a Claude Code plugin that adapts itself to your repository, then turns feature and defect delivery into an evidence-driven graph with bounded repair loops.

Instead of treating Claude as a single freeform coding assistant, Asterweave wraps it in a deterministic delivery process: the model reasons and uses tools inside one graph node at a time, while plain Node.js scripts own workflow state, attempt budgets, evidence records, typed transitions, destructive-command guardrails, and the stop gate. A task is only considered done when acceptance criteria, tests, runtime verification, independent reviews, and pull-request state all have current, environment-grounded evidence — not a model's claim that it is done.

Asterweave does not impose Clean Architecture, DDD, CQRS, MVVM, or Redux on your codebase. It discovers and preserves whatever architecture is already there.

What it actually does​

  • Scaffolds repository context. /asterweave:scaffold reads your code, tests, CI, and existing instructions, then proposes (and, after your approval, writes) an evidence-backed CLAUDE.md, .claude/rules/, project skills/agents, and .claude/asterweave.json — never a generic template.
  • Runs a graph, not a chat. /asterweave:deliver walks a fixed sequence — intake, analyze, challenge, plan, human approval, implement, test, verify, review, submit PR, monitor CI, resolve review comments, update the work item — recorded in .claude/asterweave/state.json and an append-only event ledger.
  • Delegates to specialist agents. Thirteen narrowly scoped subagents (read-only analyzers and reviewers, write-capable implementers and testers) do the bounded work for each node, with least-privilege tool access enforced per agent.
  • Talks to your issue tracker and Git host. A bundled GitHub MCP server (and an optional Azure DevOps MCP server) handles issues/work items, pull requests, CI checks, and review comments — every write is previewed, confirmed, and read back for verification.
  • Enforces safety deterministically. A PreToolUse hook blocks a known set of destructive shell commands; a Stop hook keeps an active workflow moving (or lets the turn end cleanly at approval or a blocked state) instead of silently abandoning it.

What it is not​

  • It is not a fully autonomous engineer that merges its own work. It pauses for human approval after challenge/plan, and again before commit/push/PR unless you explicitly pass --auto-pr. It never merges, self-approves, dismisses reviews, bypasses required checks, force-pushes, or deletes branches.
  • It is not a code generator that ignores your repository's conventions. Repository routing in .claude/asterweave.json can specialize or tighten Asterweave's graph, but it cannot disable approval, evidence, testing, verification, review, security, or Git-safety gates.
  • It is not a spec-authoring tool by default. Asterweave never generates a specs/ directory; it only reads and links to one your repository already has, or proposes a single use case for a normal/complex feature under explicit approval.

Where to go next​