By 23min
Milestone-lifecycle skills and role agents for aiwf. Wraps aiwf's planning verbs with opinionated rituals (TDD-driven milestone start, contract-checked milestone wrap, release tagging, in-flow ADR/decision recording, tracking-doc convention).
Implements aiwf milestone acceptance criteria via TDD. Writes code and tests; one-off patches; starts and advances milestones; closes milestones at wrap. Never commits without explicit human approval.
Releases aiwf epics — semver bump, CHANGELOG update, annotated git tag, post-release health checks. Runs after `aiwfx-wrap-epic` has closed the epic and merged to mainline. Never tags or pushes without explicit human approval.
Plans aiwf epics and milestones. Scopes work, sequences milestones, captures decisions. Drives planning conversations and produces specs; never commits without explicit human approval.
Reviews code changes for correctness, AC coverage, branch-coverage discipline, conventions, and documentation hygiene. Reconciles status surfaces and verifies milestone or epic wrap. Emits approve / request-changes verdict with file:line references.
Closes an aiwf milestone — verifies all ACs met, runs scoped doc-lint, finalizes the tracking doc, promotes status to done, prepares the wrap commit. Use when the user says "wrap M-NNN" or "finish the cache milestone" and self-review per `aiwfx-start-milestone` has passed. Commit and push require explicit human approval.
Closes an aiwf epic — verifies all milestones done, scaffolds a wrap artefact, harvests ADR candidates, runs scoped doc-lint, merges the epic branch into mainline, promotes the epic to done. Use when the user says "wrap E-NN" or "close the auth epic" and every milestone in the epic is wrapped. Commit and push require explicit human approval.
Scopes, refines, and documents a new aiwf epic. Allocates the next E-NN id via `aiwf add epic`, scaffolds an epic spec from the plugin's template, fills in goal/context/scope/constraints/success criteria, and stages the spec for the user's review. Use when the user says "plan feature X", "design the system for Y", or "I need to build Z". Calls aiwf — install only with the aiwf-extensions plugin.
Decomposes an approved aiwf epic into a sequenced set of independently-shippable milestones. Allocates each M-NNN via `aiwf add milestone --epic E-NN`, scaffolds each milestone spec from the plugin's template, sequences them by dependency. Use after `aiwfx-plan-epic` when the user says "break this into milestones" or "plan the work for E-NN".
Records a decision that surfaces during planning, implementation, or review — as an ADR (architectural, long-lived) or as an aiwf D-NNN entity (project-scoped). Allocates the id via `aiwf add`, fills the body from the appropriate plugin template, commits. Invoke in-flow whenever a decision worth keeping for future readers becomes clear; the calling skill (start-milestone, wrap-milestone, review-code, plan-epic, etc.) just hands off and continues.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Claude Code plugin marketplace shipping engineering-ritual skills and role agents that complement aiwf.
Pre-alpha. Marketplace and plugin manifests scaffolded; no skills shipped yet.
aiwf is a narrow planning kernel: six entity kinds (epic, milestone, ADR, gap, decision, contract), stable IDs, validators, git-trailer history. It deliberately has no opinion about how the work gets done — branching, TDD, code review, milestone lifecycle, release ceremonies.
This repo ships those opinions, separately, as Claude Code plugins. Two plugins, both optional:
| Plugin | Contains | When to install |
|---|---|---|
| aiwf-extensions | Milestone-lifecycle skills (aiwfx-start-milestone, aiwfx-wrap-milestone, aiwfx-wrap-epic, aiwfx-release, aiwfx-track, aiwfx-record-decision, …) plus four role agents (planner, builder, reviewer, deployer) | If you use aiwf as your planning kernel and want the milestone-driven engineering loop |
| wf-rituals | Generic engineering rituals (wf-patch, wf-tdd-cycle, wf-review-code, wf-doc-lint) | If you want the engineering rituals on their own — works on any repo, with or without aiwf |
In a Claude Code session, from inside a consumer repo:
/plugin marketplace add 23min/ai-workflow-rituals
/plugin install aiwf-extensions@ai-workflow-rituals
/plugin install wf-rituals@ai-workflow-rituals # optional
Updates: /plugin update <name>@ai-workflow-rituals. Auto-update on startup is enabled by default while the marketplace is in active development.
Claude Code asks where to install. Pick Project scope by default. It writes .claude/settings.json into the consumer repo, which means:
User scope is only right if you're sure you want these plugins available in every project on your machine. Local scope (gitignored) is right for short-term experimentation in a single repo.
For the planning kernel itself, see ai-workflow-v2:
go install github.com/23min/ai-workflow-v2/tools/cmd/aiwf@latest
aiwf init # in your consumer repo
The two plugins differ in how tightly they couple to aiwf. This is deliberate.
aiwfx-* skills — call aiwf shell verbs, reference aiwf's ID format (E-NN, M-NNN, …), use aiwf's status vocabulary. By definition coupled. If you don't use aiwf, this plugin is dead weight.wf-* skills — speak the language of the work (milestone, acceptance criteria, branch, test, PR) without mentioning aiwf, its IDs, its status vocabulary, or its directory layout. By design they survive an aiwf swap. They work the same against a repo using aiwf, against a repo using a different planning kernel, or against a repo using none.This is a discipline, not an enforcement. Every wf-* skill goes through a coupling-boundary review at port time: "if aiwf were deleted tomorrow, would this skill still make sense?" If no, it belongs in aiwfx-*.
ai-workflow-rituals/
├── .claude-plugin/
│ └── marketplace.json
├── plugins/
│ ├── aiwf-extensions/
│ │ ├── .claude-plugin/plugin.json
│ │ ├── skills/aiwfx-*/SKILL.md
│ │ ├── agents/{planner,builder,reviewer,deployer}.md
│ │ └── templates/
│ └── wf-rituals/
│ ├── .claude-plugin/plugin.json
│ ├── skills/wf-*/SKILL.md
│ └── templates/
├── README.md
└── CHANGELOG.md
Each plugin's directory layout follows Claude Code's plugin reference. Contents are auto-discovered.
| Plugin | Stage |
|---|---|
| Marketplace manifest | scaffolded |
aiwf-extensions plugin manifest | scaffolded |
wf-rituals plugin manifest | scaffolded |
aiwf-extensions skills | not started |
aiwf-extensions agents | not started |
aiwf-extensions templates | not started |
wf-rituals skills | not started |
wf-rituals templates | not started |
The porting plan and the rationale for what's in scope vs. deferred lives in ai-workflow-v2/docs/rituals-plugin-plan.md.
Apache-2.0. See LICENSE.
npx claudepluginhub 23min/ai-workflow-rituals --plugin aiwf-extensionsRepo-agnostic engineering rituals: branching (patch/fix/chore), TDD cycle, code review, doc hygiene. Speaks the language of the work (milestone, AC, branch, test, PR) without coupling to any specific planning kernel.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Comprehensive startup business analysis with market sizing (TAM/SAM/SOM), financial modeling, team planning, and strategic research
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.
Complete creative writing suite with 10 specialized agents covering the full writing process: research gathering, character development, story architecture, world-building, dialogue coaching, editing/review, outlining, content strategy, believability auditing, and prose style/voice analysis. Includes genre-specific guides, templates, and quality checklists.
Comprehensive .NET development skills for modern C#, ASP.NET, MAUI, Blazor, Aspire, EF Core, Native AOT, testing, security, performance optimization, CI/CD, and cloud-native applications
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses