build-right

Apply Build Right engineering principles as a planning, implementation, and review standard. Use when Codex is choosing technologies, service boundaries, storage models, architecture boundaries, splitting modules or features, creating public contracts, changing provider adapters, reviewing implementation quality or over-engineering risk, planning tests, handling side effects, errors, observability, security, or deciding whether markdown guidance needs enforceable checks.

Execute one bounded task using baseline evidence, narrow implementation, verification, evidence capture, and tracker updates. Use when the user invokes /build-right-execution, wants to work the next issue, run an evidence-driven implementation loop, verify a task, update task state, or continue execution from a prepared task queue.

Maintain Build Right feature planning after preflight and before execution. Use when the user wants to explore a desired feature, groom or reprioritize backlog/sprint work, run bounded product or technical research, use subagents for planning review, create or split execution-ready tasks, update planning evidence, or hand off a ready task to build-right-execution without implementing product code.

Guide founder/product pre-execution setup before AI implementation. Use when the user invokes /build-right-preflight, wants to bootstrap a blank or existing project, capture founder intent, validate assumptions, create product truth, define MVP scope, create operating docs, create Sprint 0 tasks, or prepare the first executable AI task.

Answer one unresolved logic or UI design question with disposable executable evidence. Use for explicit prototype, spike, proof-of-concept, interaction experiment, state-model experiment, or design-experiment requests where observed behavior can reduce uncertainty before production feature planning.

Maintain a durable multi-session decision map when the destination is meaningful but the implementation path cannot yet fit in one trustworthy planning session. Use only when the user explicitly invokes this skill for a foggy effort that needs research, prototypes, founder decisions, or technical decisions before feature planning.