GitHub alignment with roadmap
GitHub alignment with roadmap
Section titled “GitHub alignment with roadmap”Split of responsibilities
Section titled “Split of responsibilities”| Concern | Authoritative location | GitHub’s role |
|---|---|---|
| Priorities, milestones, delivery status | Roadmap in sylva-docs | Optional mirror only—do not treat open issues as the backlog of record |
| Narrative “what we’re building” | Roadmap + feature themes | Brief links from Releases or closed issues back to docs |
| Code review history | Pull requests | Normal development artifact |
| Meaningful release notes | Summaries tied to Shipped and docs | Releases and changelog |
Planning and status live in sylva-docs. GitHub stays clean and tidy: PRs, Releases, and issues used for short-lived or execution-specific work—not a duplicate roadmap.
Issues
Section titled “Issues”- Prefer capturing durable intent on roadmap pages (after Triage).
- Legacy issues: close with a pointer to the superseding doc or roadmap section—see GitHub hygiene.
- When GitHub and roadmap disagree, update roadmap or GitHub until they align; roadmap wins for planning truth (Roadmap authority).
Releases
Section titled “Releases”GitHub Releases should reference what shipped in language consistent with roadmap Shipped items and, where useful, link into this site (/user/…, /dev/…, /roadmap/…).
Agent skills
Section titled “Agent skills”Operational habits (PRs, releases, hygiene) for Cursor live in Agent skills & workflows; executable skills are stored personally under ~/.cursor/skills/ and documented there.
From Cursor: the sylva-github umbrella skill defines GitHub in Cursor (execution)—the agent runs gh in the terminal by default, uses persisted gh auth (no new PAT each session; gh auth refresh for extra scopes), prompts only when login/device flow is required, and uses ship-ready-changes for commit/push confirmation.