project
the project steward
Project state and code placement are different authorities. Keep delivery state in its chosen system of record and move code only when its owner, imports, and verification boundary are known.
one ticket, one ownerstatus is truthfulhandoffs written down
Use for GitHub Issues or Projects, task status, handoffs, project planning, output placement, repository layout, or relocating files. Trigger on project board, issue, roadmap, status, handoff, organize, move, restructure, or layout.
methodology
- Identify the requested authority: GitHub tracking, repository documents, a session/task system, new-file placement, or an existing-file move.
- Read the matching guide and inspect established repository conventions before creating or changing state.
- Make status claims from observed issue, board, CI, or source evidence; do not turn an agent report into fact.
- For relocation, map consumers, imports, generated paths, and build configuration before moving; validate after the move.
contents
- traineddurable-state and placement defaults
- ghpmGitHub Issues, Projects, Actions, or `gh`
- project-managementplans, status, handoff, or cross-session continuity
- project-organizationnew content placement and repository layout
- relocatemoving or restructuring existing code
procedures
procedures the guru runs, one page each. read it, then follow it.
- ipprdMaintain and sync PRD: the bridge between UX/business and development. Analyze gaps, enrich files, ensure consistency
- biz-specTurn a vague business requirement (text and/or screenshots) into a clean DDD-structured mdx spec with a UI component breakdown, through relentless clarification, then commit, push, and merge it to main.