Tier Rename Decision
Tier Rename Decision
Section titled “Tier Rename Decision”Date: 2026-03-21 Status: confirmed, not yet applied
Old tiers
Section titled “Old tiers”- Hobby
- Professional
- Enterprise
New tiers
Section titled “New tiers”- Basic — context + guardrails (docs, standards, session management — no scaffolder CLI required)
- Project Management — with scaffolder (full
sc createexperience, CLI tools, templates) - Plane Integrated — PM tools with Plane integration (bidirectional sync, work tracking, milestones)
What needs updating when applied
Section titled “What needs updating when applied”templates/project-root/STANDARDS.md— all tier referencestemplates/project-root/CLAUDE.md— if tier is mentionedsrc/—sc createprompts, any tier logic in CLIREADME.md— workflow table, tier descriptionsCHAT-REFERENCE.md— branch rules by scale tier section- Plane integration docs (when they exist)
- Discussed previously but never documented
- Branch strategy per tier stays the same, just the names change
- Basic tier may not need staging branch at all
- Plane integration tier is new — defines when Plane sync is active vs optional