Central source of truth for all reusable engineering agents, standards, templates, and playbooks. Every project in the organization uses this platform — agents are loaded here, project context is injected at runtime.
Core principle: Agents contain no project-specific knowledge. Context is always injected. GitHub is the system of record. Work is organized into workstreams that move through defined lifecycle states.
| What you want to do | Start here |
|---|---|
| Understand the daily workflow | docs/daily-operating-system.md |
| Review all active work | review backlog |
| Capture a new idea | capture idea: <description> |
| Bootstrap a new workstream | bootstrap WS-XXX {project-type} — see docs/workstream-bootstrap-protocol.md |
| Start new work | create workstream — create a GitHub issue using .github/ISSUE_TEMPLATE/ |
| Onboard an existing project | onboard existing project — see playbooks/existing-project.md |
| Run a command | docs/command-interface.md |
| Understand lifecycle states | docs/lifecycle-states.md |
| Understand the platform | docs/platform-overview.md |
| Read the platform charter | platform-charter.md |
| Start a new project | playbooks/new-project.md |
| Find the right agent | docs/agent-catalog.md |
| Understand agent rules | docs/governance.md |
Ideas are the lightest entry point. Workstreams are the execution unit. Lifecycle state determines what happens next.
idea → intake → defined → designed → planned → implementing → validating → reviewing → ready-to-ship → shipped
| Command | What it does |
|---|---|
capture idea |
Log a new idea — no workstream, no WIP cost |
promote idea |
Convert an idea into a workstream at intake |
review backlog |
Full view of ideas + workstreams; surfaces next action |
status project |
Project health — blockers, priorities, open ideas |
| Command | What it does |
|---|---|
create workstream |
Create a new workstream; set state to intake |
define requirements for WS-[ID] |
Solution Lead produces requirements; state → defined |
design system for WS-[ID] |
Architect produces architecture; state → designed |
create backlog for WS-[ID] |
Product Owner produces sprint backlog; state → planned |
implement WS-[ID] |
Senior SSE builds the feature; state → implementing |
validate WS-[ID] |
Tester verifies acceptance criteria; state → validating |
review WS-[ID] |
Code Reviewer quality gate; state → reviewing |
ship WS-[ID] |
Delivery Engineer + DevOps merge and deploy; state → shipped |
status WS-XXX |
Current state, blockers, next command |
bootstrap WS-XXX |
Full pipeline — intake to shipped in one command |
Full reference: docs/macro-reference.md · State definitions: docs/lifecycle-states.md
Every workstream starts as a GitHub issue.
| Template | Use when |
|---|---|
| feature_workstream.md | New user-visible functionality |
| bug_workstream.md | Defect — behavior differs from specification |
| refactor_workstream.md | Code restructuring without behavior change |
| research_workstream.md | Time-boxed investigation |
| Agent | Role |
|---|---|
| Orchestrator | Workstream coordination — tracks status, enforces WIP limits; does NOT design or implement |
| Product Owner | Backlog, sprint planning, acceptance criteria |
| Solution Lead | Requirements definition, solution framing, feasibility |
| Agent | Role |
|---|---|
| Architect | System design, ADRs, alternatives analysis |
| Senior Software Engineer | Implementation, scaffolding |
| Agent | Role |
|---|---|
| Code Reviewer | Severity-tagged code review — quality gate |
| Tester | Test strategy, validation, defect reproduction |
| Agent | Role |
|---|---|
| Researcher | Source-cited research reports |
| Documentation | READMEs, API docs, runbooks, ADRs |
| Delivery Engineer | Branch strategy, PRs, releases, git operations |
| DevOps | Infrastructure, CI/CD, environments, observability |
| Template | Owner Agent | Description |
|---|---|---|
| workstream.md | Project Lead | Workstream record — lifecycle, dependencies, priority, feedback |
| vision.md | Solution Lead | Project vision — why we're building this |
| requirements.md | Solution Lead | Requirements document — what we're building |
| architecture.md | Architect | System design with alternatives |
| adr.md | Architect | Architecture Decision Record |
| roadmap.md | Product Owner | Product roadmap |
| sprint-backlog.md | Product Owner | Sprint backlog with tasks and DoD |
| project-status.md | Project Lead | Live project status |
| project-structure.md | Senior SSE | Standard directory layout |
| project-bootstrap.md | Project Lead | Initialization checklist |
| Playbook | When to use |
|---|---|
| new-project.md | Starting from scratch |
| existing-project.md | Onboarding an existing codebase |
| feature-development.md | Building a feature end-to-end |
| bug-investigation.md | Investigating and fixing a defect |
| release-process.md | Cutting a standard release or hotfix |
| Standard | Description |
|---|---|
| integration.md | GitHub-native execution: event mapping, label enforcement, mobile workflow |
| branching.md | Branch model, naming, protection rules, merge strategies |
| pull-requests.md | PR format, review requirements, quality gates, labels |
| issue-templates.md | Canonical label taxonomy, lifecycle |
| File | Description |
|---|---|
| docs/lifecycle-states.md | Canonical state definitions, state machine, macro→state map |
| docs/macro-reference.md | All commands: invocation, behavior, outputs, next step |
| docs/workstream-registry.md | Live global state — all active workstreams across all stages |
| docs/workstream-execution-model.md | WIP limits, scheduling, priority, context switching |
| workstreams/ | Per-workstream record files (WS-YYYYMMDD-NNN.md) |
| File | Description |
|---|---|
| docs/priority-engine.md | 5-factor scoring model, weights, override rules, dependency handling |
| docs/backlog-recommendations.md | Advisory ranked workstreams, critical path, quick wins, risk flags |
| File | Description |
|---|---|
| docs/execution-log.md | Rolling per-workstream execution record; pattern frequency |
| docs/system-improvement-log.md | Operational improvement proposals (IP-NNN lifecycle) |
| docs/system-health-dashboard.md | Executive health view: throughput, cycle time, utilization, bottlenecks |
| docs/system-change-proposals.md | Structural change proposals (SCP-NNN) with simulation reports |
| docs/learning-cycle.md | Three-level intelligence: operational + structural + strategic |
| File | Description |
|---|---|
| docs/strategic-roadmap.md | Advisory SRP proposals — distinct from binding docs/roadmap.md |
| docs/opportunity-map.md | Opportunity catalog with leverage/complexity scores and evidence |
| Doc | Description |
|---|---|
| docs/daily-operating-system.md | Daily interaction model — commands, startup routine, mobile workflow |
| docs/platform-overview.md | Full onboarding guide — read this first |
| docs/command-interface.md | All commands: purpose, inputs, outputs |
| docs/system-boundary.md | Authoritative boundary rules — active model vs. deprecated concepts |
| docs/agent-catalog.md | Agent trigger phrases and quick reference |
| docs/agent-collaboration-matrix.md | Handoff protocols and role interaction patterns |
| docs/governance.md | Authority boundaries, escalation rules, override rules |
| docs/github-event-mapping.md | GitHub event → platform action map |
| docs/system-state.md | Live merged GitHub + platform state, idea backlog |