specclaw

Just say "I have a proposal" — SpecClaw manages the full lifecycle of a code change: propose → plan → build → verify → pr. It writes structured proposals, specs, designs, and ordered task lists into your project, then drives implementation through the lifecycle with full traceability from requirement to merged PR.

Try it in 30 seconds: /plugin marketplace add chan4lk/specclaw → /plugin install specclaw@chan4lk → /specclaw:init

Why SpecClaw?

AI coding agents are powerful but lose context fast. SpecClaw gives every change a paper trail:

• proposal.md — why this change matters
• spec.md — requirements + acceptance criteria
• design.md — technical approach, file map, key decisions, risks
• tasks.md — ordered tasks, grouped into parallelizable waves
• verify-report.md — evidence the implementation meets the spec
• GitHub / Azure DevOps / Jira sync — keep external trackers up to date

Each change lives in .specclaw/changes/<name>/ in your repo. The plugin operates on your project's CWD; nothing is hidden inside the plugin install.

Installation

Requires Claude Code v2.1 or later.

/plugin marketplace add chan4lk/specclaw
/plugin install specclaw@chan4lk

Future plugins by the same owner ship in the same chan4lk marketplace — you only register it once.

Quickstart

> /specclaw:init
  Initializes .specclaw/ in the current project, generates config.yaml, creates the dashboard.

> /specclaw:propose "add dark mode support"
  Drafts .specclaw/changes/add-dark-mode/proposal.md for your review.

> /specclaw:plan add-dark-mode
  Generates spec.md, design.md, tasks.md once the proposal is approved.
  Append --author-spec to author spec.md interactively via the spec-author subagent, with an approval gate before design.md / tasks.md.

> /specclaw:build add-dark-mode
  Executes tasks wave-by-wave, committing each.

> /specclaw:verify add-dark-mode
  Runs tests/lint/build, evaluates against acceptance criteria, writes verify-report.md.

> /specclaw:pr add-dark-mode
  Opens a GitHub PR using the spec + verify report as the description.

Project Structure

When initialized in a project, SpecClaw creates:

.specclaw/
├── config.yaml          # Project config (models, git strategy, integrations)
├── STATUS.md            # Cross-change dashboard
├── patterns.md          # Recurring pattern registry (cross-change)
└── changes/
    └── <change-name>/
        ├── proposal.md      # Problem + solution + scope
        ├── spec.md          # Requirements + acceptance criteria
        ├── design.md        # Technical approach + file map
        ├── tasks.md         # Ordered tasks with status markers
        ├── status.md        # Per-change progress tracking
        ├── errors.md        # Build error journal (auto-generated on failures)
        ├── learnings.md     # Build learnings (spec gaps, patterns, insights)
        └── verify-report.md # Verification results

Commands

All commands are namespaced under /specclaw:. Most are model-invokable — Claude will route conversationally (e.g. "i have a proposal" fires /specclaw:propose). Auth setup commands (/specclaw:auth-azdo, /specclaw:auth-jira) are explicit-only because they handle credentials.