{
  "markdown": "# Claude Code Platform\n\nA high-quality **Claude Code plugin** for repeatable, evidence-first development workflows.\n\n## Core principles\n\n1. **Single runtime charter** — one short, authoritative operating contract via `CLAUDE.md`\n2. **Deterministic guardrails** — settings, permissions, and hooks enforce critical behavior\n3. **9-phase workflow** — Intake → Review → Consensus → Tech Spec → Todo Plan → Implementation → Verification → Milestone Closure → Session Handoff\n4. **Evidence-first verification** — never claim completion without proof\n5. **Install once, use everywhere** — plugin works across all your projects\n\n---\n\n## Installation\n\n### From local path\n```bash\nclaude --plugin-dir ./path/to/claude-forge\n```\n\n### From marketplace (when published)\n```bash\n/plugin install claude-forge\n```\n\n### Verify\nOnce installed, these skills become available:\n```\n/claude-forge:bootstrap\n/claude-forge:review\n/claude-forge:test\n/claude-forge:gap-note\n/claude-forge:milestone-report\n/claude-forge:session-handoff\n```\n\n---\n\n## What this plugin provides\n\n### Skills (6)\n| Skill | Description |\n|-------|-------------|\n| `bootstrap` | Run health check, summarize readiness, recommend next step |\n| `review` | Orchestrate multi-review pass from requirements through consensus |\n| `test` | Run structured verification with actual command outcomes |\n| `gap-note` | Record spec-vs-reality divergence during implementation |\n| `milestone-report` | Produce standardized milestone completion report |\n| `session-handoff` | Generate precise handoff packet for next session |\n\n### Agents (3)\n| Agent | Description |\n|-------|-------------|\n| `requirement-analyst` | Transform requests into implementation-ready requirement packages |\n| `tech-spec-reviewer` | Stress-test tech specs against requirements and codebase reality |\n| `verification-auditor` | Audit claimed progress with evidence before milestone closure |\n\n### Hooks\n- **Stop hook** — prevents session exit when completion is claimed without evidence\n\n### Settings\n- Safe defaults: allows git status/diff, test commands; denies .env reads, curl, git push\n\n---\n\n## Quick start\n\n```bash\n# 1. Install the plugin\nclaude --plugin-dir ./claude-forge\n\n# 2. In your project, run bootstrap\n/claude-forge:bootstrap\n\n# 3. Start with Phase 0 — Intake\n```\n\n---\n\n## Plugin structure\n\n```\nclaude-forge/\n├── .claude-plugin/\n│   └── plugin.json              # Plugin manifest\n├── skills/                      # Plugin skills\n│   ├── bootstrap/SKILL.md\n│   ├── review/SKILL.md\n│   ├── test/SKILL.md\n│   ├── gap-note/SKILL.md\n│   ├── milestone-report/SKILL.md\n│   └── session-handoff/SKILL.md\n├── agents/                      # Plugin agents\n│   ├── requirement-analyst.md\n│   ├── tech-spec-reviewer.md\n│   └── verification-auditor.md\n├── hooks/\n│   └── hooks.json               # Plugin hooks\n├── settings.json                # Plugin default settings\n├── scripts/                     # Health check & evaluation scripts\n├── docs/                        # Reference documentation\n├── examples/                    # Example scenarios\n├── evals/                       # Self-evaluation scaffolding\n├── CLAUDE.md                    # Runtime charter\n└── README.md\n```\n\n---\n\n## Artifacts\n\nAll workflow artifacts are stored in your project's `artifacts/` directory with timestamped filenames:\n\n| Artifact | Directory | Phase |\n|----------|-----------|-------|\n| Requirement Brief | `artifacts/specs/` | 0 |\n| Consensus Matrix | `artifacts/reviews/` | 2 |\n| Final Tech Spec | `artifacts/specs/` | 3 |\n| Todo Plan | `artifacts/plans/` | 4 |\n| Gap Note | `artifacts/gap-notes/` | 5+ |\n| Verification Report | `artifacts/verification/` | 6 |\n| Milestone Report | `artifacts/reports/` | 7 |\n| Session Handoff | `artifacts/handoffs/` | 8 |\n\n---\n\n## Documentation\n\n- [Framework Reference](docs/framework-reference.md) — detailed workflow and artifact schemas\n- [Architecture](docs/architecture.md) — layer model and design rationale\n- [Customization](docs/customization.md) — how to adapt without breaking core\n- [Platform Roadmap](docs/platform-roadmap.md) — evolution path\n\n---\n\n## Troubleshooting\n\n### `doctor.sh` shows blockers\nFix the reported missing files or settings first.\n\n### Plugin skills not showing\nRun `/reload-plugins` or restart Claude Code. Skills should appear as `/claude-forge:<skill-name>`.\n\n### Claude sees built-in agents but not plugin agents\nVerify the plugin is loaded with `claude --debug`. Check that agent `.md` files are in `agents/`.\n\n### I need stronger enforcement\nAdd more permission rules to `settings.json`.\n",
  "bytes": 4560,
  "sha": "0c86fc46a7d164451aab5537ab376d1c20cddcaef5b1b8c5c9ef2070ddc9a1ad",
  "repo_slug": "junghyunryu/claude-forge",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_junghyunryu_claude_forge_claude_forge_910de8dc/readme"
}