jpmschweitzerandClaude Opus 4.6
7158ae9cf5
Claude-native starter kit that bootstraps multi-agent team infrastructure for any project. Clone once, install as a global skill, run /kit-install in any project directory. Includes: - 3-tier profile system (minimal/standard/full: 3-12 agents) - 16 agent archetype templates with personality spectrum - 18 skill templates using domain-action naming convention - Stakeholder persona panel for workshops and PR reviews - SQLite ticketing DB with CLI tools (config-based DB paths) - Decision tracking, sprint lifecycle, workshop orchestration - Multi-git-host support (GitHub, Gitea, GitLab) - /kit-update skill for syncing with source repo evolution - Naming theme support for agent identity/flavor - Smoke tests for all three profile tiers Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.1 KiB
2.1 KiB
Sprint Briefing Template
Each team gets one briefing file at docs/sprints/sprint-N/<team>.md.
File structure
# Sprint N: <Theme> — <Team> Tasks
**Goal:** <One-sentence sprint goal, shared across all teams>
**Branch:** `<team>`
**Agents:** <Agent names and roles>
## Carry-over from Sprint N-1
(Only if there are incomplete tickets from the previous sprint)
| # | Title | Status | Notes |
|---|-------|--------|-------|
| #ID | Title | status | Why it carried over |
## New Tickets
| # | Title | Blocked by |
|---|-------|------------|
| #ID | Title | #dependency or — |
Use `db/connectors/ticket show <id>` for full details.
## Key Decisions
- `decisions/<domain>.md` — D-NNN (short name), D-NNN (short name)
## Open Questions to Resolve Early
(Only if there are Q-NNN items that block sprint tickets)
- **Q-NNN: Title** — Brief context. Resolve before #ID starts.
## Notes
One bullet per ticket with:
- What exists already (files, modules, stubs)
- What the ticket actually needs to deliver
- Integration points with other tickets
- Non-obvious gotchas
## Dependency Chain
#A (name) → #B (name) → #C (name) #D (name) → standalone, parallel track
## PR Workflow
When ready to submit, create a PR using the git host CLI configured for your
project (see CLAUDE.md). All flags must be explicit to avoid interactive prompts.
Joint briefing extras
The joint.md file additionally includes:
- Pre-Sprint table: decisions/schema work that must happen before implementation
- Sprint Completion Proof: concrete observable criteria (what you can see/do when the sprint is done)
- Test plan alignment with project testing phases
Team assignments
| Team | Branch | Agents | Scope |
|---|---|---|---|
| backend | server |
Backend Dev, Architect | Server-side systems |
| frontend | client |
Frontend Dev, Architect | Client UI and rendering |
| joint | both | All implementation agents | Integration, proofs, cross-team work |
| content | (varies) | Content authors, domain experts | Content authoring |