Claude project template

The framework I use across all my projects

Claude project template is the skeleton I clone at the start of every new project. It wires a dev framework around Claude Code built on one simple cycle:

/next-issue → /start-issue → code → /open-pr → /merge-pr

Project tracking — issues, ADRs, sprints — lives in a local Obsidian vault, in strict YAML frontmatter. Code, PRs and CI stay on GitHub. A lightweight CI bridge keeps the vault note in sync when a PR merges, even from GitHub's web interface. No dependency on GitHub Projects v2, which saturates the GraphQL quota too quickly.

Why a vault instead of Projects v2

ADRs and grooming carry strategy; I'd rather keep them in a private, versioned space that's readable offline in Obsidian than in a proprietary tool. The vault is the source of truth for the what and the why; GitHub stays the source of truth for the code. The Kanban board is just an Obsidian Bases view grouped by status.

A ticket's life cycle

A PM hat (/roadmap) sets the vision and prioritizes epics. A PO hat (/groom) breaks an epic into well-formed issues, straight into vault notes. Then /next-issue picks the next ready issue, /start-issue creates the branch and flips status to in-progress, and after implementation /open-pr then /merge-pr run the reviewer, wait for green CI and squash-merge. A pre-push hook blocks direct pushes to main.

Migrating an existing project

The template ships scripts to move a running project onto this workflow: import GitHub issues (open + closed, REST only), convert legacy ADRs to YAML frontmatter with cross-reference patching. My Luchamon bot was migrated through this very chain — 156 issues and 23 ADRs at once.

This template has no public roadmap: it evolves with the best practices I define in my active projects, like Orfeo and Luchamon Bot.