feat(harness): sprint tracking convention + README overhaul - #3
Merged
Merged
Conversation
Sprint tracking (per-project): - Add sprints/ directory convention with CURRENT symlink per project - Extend templates/sprint-plan.md: frontmatter (status, dates, goal), milestone grouping, PR-links column, in-file retrospective section - Rewrite /sprint-plan: auto-detect next sprint number, write to sprints/sprint-NNN.md (fixes prior bug writing to specs/), repoint CURRENT - Rewrite /retro: read CURRENT, stamp closed_date + status: closed, write retro into same sprint file (no separate retro-*.md) - Document convention in CLAUDE.md under Multi-Client Governance README overhaul: - Add badges, What It Is, How It Works with Mermaid pipeline flow - Add full 25-agent team roster table with Hardware Council - Add Mermaid team hierarchy and sprint git-flow diagrams - Document directory structure, getting started, key commands - Explain the six non-negotiable workflow gates - Document sprint tracking convention - Document scripts/sync-to-public.sh usage and PII guard - Add contributing guidelines
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two coordinated changes on one branch.
Sprint tracking (per-project)
sprints/directory under eachclients/<slug>/projects/<slug>/CURRENTsymlink always points at the active sprint filetemplates/sprint-plan.mdextended with frontmatter (status, dates, goal), milestone grouping, PR-links column, and an embedded retrospective section/sprint-planrewritten: auto-detects next sprint number, writes tosprints/sprint-NNN.md(fixes prior bug writing tospecs/), repointsCURRENT/retrorewritten: readsCURRENT, stampsclosed_date+status: closed, writes retro into the same sprint file (no separate retro doc)CLAUDE.mdupdated under Multi-Client GovernanceREADME overhaul
scripts/sync-to-public.shusage and PII guard documentedTest plan
/Users/,clients/self, orrdemerittreferences slip through)/sprint-planagainst a test project and confirmsprints/sprint-001.mdis created andCURRENTsymlink is correct/retroand confirm the active sprint flips tostatus: closedwithclosed_datestamped and retro filled