Skip to content

majiayu000/spellbook / skills/dev-architecture-playbook

dev-architecture-playbook

Verified

Route full software-development architecture work from product intent through design, implementation, testing, release, and operations. Use when the user asks for a complete development architecture, wants to know which Spellbook skills to combine, needs an execution path across PRD/spec/API/data/security/performance/release/SRE, or asks to turn an idea or repo into a production-ready engineering plan.

Dev Architecture Playbook

Purpose

Use this as the lifecycle router before starting broad product or architecture work. It chooses the minimum useful skill chain, defines gates, and prevents starting implementation before the required contracts exist.

Route

Classify the request first:

RequestPrimary SkillsOutput
Idea, product direction, or market/user problemproduct-discovery, prd-masterProduct brief, user stories, success metrics
Architecture or module boundariesarchitecture-foundation, technical-spec, elegant-architectureArchitecture spec, boundaries, rejected alternatives
API, auth, data, or schema contractapi-design, auth-security, database-patterns, data-contract-migrationsVersioned contracts and migration plan
UI/product surfacefrontend-design, ui-ux-pro-max, ui-design-system, playwright-automationUX flow, component plan, visual checks
Implementation workflowflowguard, threads, systematic-debugging, comprehensive-testingBounded execution, ownership, root-cause debugging, and verification
Quality and regression riskcomprehensive-testing, codebase-audit, vibeguard, project-health-auditorTest matrix and risk list
Release and operationsrelease-engineering, config-secrets-environments, performance-capacity, incident-slo-runbook, observability-sre, devops-excellenceRollout, config, capacity, SLO, runbook

Required Gates

Do not treat the architecture as complete until these gates are explicit:

  1. Goal and non-goals.
  2. Domain model and ownership boundaries.
  3. External API, data, and config contracts.
  4. Security and permission model.
  5. Test strategy with command-level verification.
  6. Release, rollback, and migration gates.
  7. Observability, SLO, and incident response.

If a gate is irrelevant, state why. Do not silently skip data, security, or rollback gates for production systems.

Execution Pattern

Use this sequence for greenfield or major refactors:

  1. Product: write the product brief or PRD.
  2. Architecture: define modules, runtime boundaries, and tradeoffs.
  3. Contracts: define API, data, config, and security contracts.
  4. Plan: split work into independently verifiable steps.
  5. Implement: use one workflow skill per step, not every skill at once.
  6. Verify: run build, typecheck, tests, and focused behavioral checks.
  7. Release: define rollout, migration, rollback, monitoring, and support owner.

For existing repos, start with repo-agent-context-audit or codebase-audit before proposing new structure.

Output Shape

Return a compact plan:

goal:
context:
selected_skill_chain:
architecture_gates:
implementation_steps:
verification_commands:
release_and_ops_gates:
open_risks:

Prefer the smallest chain that covers the risk. Too many skills at once usually means the scope needs to be split.

rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall