shrwnsan/tempo
Safety-proportional process for agentic SDLC: trivial changes skip ceremony, risky changes earn it. Risk-tiered loop with fail-twice auto-promotion and a verify-before-done hard gate.
Classify a coding task as risk tier 0, 1, or 2 before starting work, and route to the matching tier flow. Use at the start of any non-trivial task, whenever a task's risk is unclear, or after a second failed attempt on the same fix. Part of the tempo plugin.
Tier-0 trivial-change rules (typo, copy tweak, one-line fix). Rarely needs loading — the tempo session routing table already defines tier 0; load only when unsure a change qualifies as trivial.
Tier-1 standard-change flow — one-line plan note, test-first, single agent, systematic debugging on failures. Use for normal feature work and bug fixes with clear requirements. Promote to the tier-2-risky flow if the same fix fails twice. Part of the tempo plugin.
Tier-2 risky-change flow — short plan file, deliberate build, review gate and verify gate before done. Use for architectural changes, public API changes, ambiguous requirements, security/auth/data work, or after a tier-1 task failed twice. Part of the tempo plugin.