{
  "markdown": "# Claude Cadence\n\nAn issue-driven, multi-agent development workflow plugin for [Claude Code](https://docs.anthropic.com/en/docs/claude-code).\n\nClaude Cadence provides a structured development workflow with git worktrees, phased implementation, specialist agent delegation, and GitHub issue tracking — all stack-agnostic and customizable per project.\n\nThis repo also includes a thin Codex compatibility layer that reuses the existing Claude prompts, scripts, and `CLAUDE.md` as the source of truth. See [docs/codex-compatibility.md](docs/codex-compatibility.md).\n\n## Codex\n\nCodex support is packaged as a compatibility layer rather than a second copy of the workflow docs:\n\n- `.codex-plugin/plugin.json` registers the plugin for Codex\n- `codex/skills/` contains generated thin wrappers for commands, shared skills, and specialist roles\n- `scripts/sync-codex.py` regenerates those wrappers from the canonical Claude source files\n\nWhen updating Cadence workflows, edit the existing Claude files first and then run:\n\n```bash\npython3 scripts/sync-codex.py\n```\n\n## Installation\n\n### Git clone (simplest)\n\n```bash\ngit clone https://github.com/dokipen/claude-cadence.git\nclaude --plugin-dir ./claude-cadence\n```\n\nTo always load the plugin, add `--plugin-dir` to your shell alias or config:\n\n```bash\nclaude() { command claude --plugin-dir /path/to/claude-cadence \"$@\"; }\n```\n\n### Plugin marketplace\n\n```bash\n# Add the marketplace (once)\n/plugin marketplace add dokipen/claude-cadence\n\n# Install the plugin\n/plugin install claude-cadence\n```\n\n## Updating\n\n### Git clone\n\n```bash\ncd /path/to/claude-cadence && git pull\n```\n\n### Plugin marketplace\n\nRun `claude plugin update cadence@claude-cadence` to update, then restart Claude Code.\n\n## What You Get\n\n### Commands (user-invoked)\n\n| Command | Purpose |\n|---------|---------|\n| `/lead` | Coordinate implementation through 8 structured phases (0–7) |\n| `/refine` or `/refine 123` | Refine issues to quality standards |\n\n### Skills (model-invoked)\n\n| Skill | Purpose |\n|-------|---------|\n| `new-work` | Create a git worktree for isolated development |\n| `create-pr` | Create a PR with pre-flight verification |\n| `create-skill` | Bootstrap new Claude Code skills |\n| `skill-iterate` | Evaluate, benchmark, and iteratively improve an existing skill using [Anthropic's skill-creator](https://github.com/anthropics/skills/tree/main/skills/skill-creator) |\n| `project-ops` | Shared worktree management utilities |\n\n### Agents (specialist delegation)\n\n| Agent | Role |\n|-------|------|\n| `code-reviewer` | PR reviews, code quality, best practices |\n| `tester` | Test execution, bug reproduction, coverage |\n| `security-engineer` | Security audits, dependency checks |\n| `performance-engineer` | Performance profiling, optimization |\n| `claude-specialist` | Claude Code configuration, agent/skill design |\n| `ticket-refiner` | Issue quality assurance |\n\n## Project Integration\n\nClaude Cadence agents read your project's `CLAUDE.md` to discover stack-specific commands. Add a `## Verification` section:\n\n```markdown\n## Verification\nflutter analyze && flutter test\n```\n\nor:\n\n```markdown\n## Verification\ngo vet ./... && go test ./...\n```\n\nThe agents and scripts will use this command automatically.\n\n### Machine-Local Ticket Provider Config (`~/.claude/cadence.json`)\n\nYou can set provider configuration in `~/.claude/cadence.json` to avoid repeating it in every project's `CLAUDE.md`. Configuration precedence (highest to lowest):\n\n1. **Per-repo overrides** (`.repos[\"owner/repo\"]`) — overrides `CLAUDE.md`\n2. **`CLAUDE.md`** — project-level config checked into the repo\n3. **Global defaults** (top-level fields) — fallback when `CLAUDE.md` has no provider config\n4. **Built-in default** — `provider: github`\n\n**Global default** — applies to any repo that has no `## Ticket Provider` section in `CLAUDE.md`:\n\n```json\n{\n  \"provider\": \"issues-api\",\n  \"project_id\": \"my-default-project\",\n  \"api_url\": \"https://issues.example.com\"\n}\n```\n\n**Per-repo override** — overrides `CLAUDE.md` for a specific repo, identified by `owner/repo` slug derived from `git remote get-url origin`:\n\n```json\n{\n  \"repos\": {\n    \"owner/repo\": {\n      \"provider\": \"issues-api\",\n      \"project_id\": \"my-project\"\n    }\n  }\n}\n```\n\nBoth can be combined in one file. Per-repo entries take precedence over `CLAUDE.md`; global defaults only apply when `CLAUDE.md` has no provider config. `api_url` is not overridable per-repo — it belongs in `CLAUDE.md` or the global default. Use `ISSUES_API_URL` for QA/local `api_url` overrides.\n\n## Adding Project-Specific Agents\n\nAdd domain-specific agents to your project's `.claude/agents/` directory. They layer on top of the plugin's core agents:\n\n```\nyour-project/.claude/\n├── agents/\n│   ├── designer.md              # Your custom agent\n│   ├── game-mechanics-engineer.md  # Your custom agent\n│   └── tester.md                # Overrides plugin's generic tester\n```\n\nSame-name agents in your project override the plugin version.\n\n## Workflow Overview\n\nThe `/lead` command orchestrates structured phases:\n\n1. **Phase 0**: Worktree setup (isolated branch)\n2. **Phase 1**: Planning (research, task breakdown, design review)\n3. **Phase 2**: Implementation (specialist delegation)\n4. **Phase 3**: Pre-PR verification (tests, lint)\n5. **Phase 4-5**: PR creation and code review gate\n6. **Phase 6-7**: Manual QA, merge, and cleanup\n\nIssues must be refined (`/refine`) before implementation — this covers estimation, acceptance criteria, and labeling.\n\n## Conventions\n\n- **Git**: All work in worktrees, never on default branch\n- **Branches**: `<issue-number>-<description>` (e.g., `42-add-auth`)\n- **Issues**: Descriptive titles, categorized via labels\n- **Estimation**: Fibonacci scale (1, 2, 3, 5, 8, 13) — applied by `/refine`\n- **Communication**: Issue comments pre-PR, PR comments post-PR\n- **GitHub**: Always use `gh` CLI\n\n## Services\n\n### Dev Environment\n\nBring up the full local stack for manual PR QA with a single command:\n\n```bash\ncp .env.dev.example .env.dev  # fill in your secrets\ndocker compose -f docker-compose.dev.yml up --build\n```\n\nThen open **http://localhost**. See [docs/dev-environment.md](docs/dev-environment.md) for full setup instructions, GitHub OAuth configuration, and how to test a specific PR branch.\n\n### Issue Microservice\n\nA GraphQL-based ticket tracking service with CLI client. See the [Issue Microservice Documentation](services/issues/docs/INDEX.md) for setup, deployment, and usage.\n\n### Issues MCP Server\n\nAn MCP server that exposes the issues API as structured tools for Claude Code and other MCP-compatible agents — no CLI binary required. See [`services/issues-mcp/README.md`](services/issues-mcp/README.md) for setup and `.mcp.json` configuration.\n\n## License\n\nMIT\n",
  "bytes": 6743,
  "sha": "4da0ea77e8864ecad12a210f326c39dda2ecb68d70cdce7e74c56faa63fe2700",
  "repo_slug": "dokipen/claude-cadence",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_dokipen_claude_cadence_76c7a1a9/readme"
}