Add a greenfield GitHub setup baseline guide for PM and BA users in setup flow and docs

[sebastientaggart]

Teams starting from scratch need clear, practical GitHub configuration guidance to use Code Cannon effectively, especially around labels for QA status and milestones for planning. This change will add a concise baseline guide aimed at program managers and business analysts so they can configure labels and milestone conventions in a way that aligns with how /start and /qa behave.

[sebastientaggart]

Agent Implementation Notes

• Update to include a greenfield-focused GitHub baseline for PM/BA users:
  • Recommended starter label taxonomy for issue triage and QA lifecycle.
  • Explicit guidance for label dependencies (, , ).
  • Milestone setup recommendations (when to set vs rely on auto-detect).
• Extend setup label population flow with a branch for low/empty label inventories in new repositories, including suggested starter labels and safe creation of missing labels.
• Update comments with a compact greenfield quick baseline so first-time teams get immediate recommendations in config.
• Update with a PM/BA-oriented mini guide that explains the GitHub setup expectations tied to and behavior.
• Run
  [claude] → .claude/commands/
  ✓ qa (updated → /Users/sebastien/dev/projects/CodeCannon/.claude/commands/qa.md)
  ✓ release (updated → /Users/sebastien/dev/projects/CodeCannon/.claude/commands/release.md)
  ✓ review-agent [prompt] (up to date)
  ✓ review (up to date)
  ✓ setup (up to date)
  ✓ ship (updated → /Users/sebastien/dev/projects/CodeCannon/.claude/commands/ship.md)
  ✓ start (up to date)
  ✓ status (up to date)
  ✓ version (updated → /Users/sebastien/dev/projects/CodeCannon/.claude/commands/version.md)

[cursor] → .cursor/rules/
⚠ qa (file exists but was not generated by Code Cannon sync — skipping, use --force to overwrite)
⚠ release (file exists but was not generated by Code Cannon sync — skipping, use --force to overwrite)
✓ review-agent [prompt] (up to date)
⚠ review (file exists but was not generated by Code Cannon sync — skipping, use --force to overwrite)
⚠ setup (file exists but was not generated by Code Cannon sync — skipping, use --force to overwrite)
⚠ ship (file exists but was not generated by Code Cannon sync — skipping, use --force to overwrite)
⚠ start (file exists but was not generated by Code Cannon sync — skipping, use --force to overwrite)
⚠ status (file exists but was not generated by Code Cannon sync — skipping, use --force to overwrite)
⚠ version (file exists but was not generated by Code Cannon sync — skipping, use --force to overwrite)

Done. after editing skills so generated files stay consistent with source skills.

• Validate generated output and run ./sync.sh --validate
  Validation passed — all placeholders are defined. for quality gates before handing off.

[sebastientaggart]

Agent Implementation Notes (Corrected)

• Update skills/setup.md to include a greenfield-focused GitHub baseline for PM/BA users:
  • Recommended starter label taxonomy for issue triage and QA lifecycle.
  • Explicit guidance for /qa label dependencies (QA_READY_LABEL, QA_PASSED_LABEL, QA_FAILED_LABEL).
  • Milestone setup recommendations (when to set DEFAULT_MILESTONE vs rely on auto-detect).
• Extend setup label population flow with a branch for low/empty label inventories in new repositories, including suggested starter labels and safe creation of missing labels.
• Update templates/codecannon.yaml comments with a compact greenfield quick baseline so first-time teams get immediate recommendations in config.
• Update README.md with a PM/BA-oriented mini guide that explains the GitHub setup expectations tied to /start and /qa behavior.
• Run ./sync.sh after editing skills so generated .claude/commands/ files stay consistent with source skills.
• Validate generated output and run make check for quality gates before handing off.