build-right-feature-planning

Build Right Feature Planning

Use this skill after preflight has created product truth, operating rules, and a task surface, and before execution starts implementation.

Core rule:

Explore the feature.
Clarify only what changes the plan.
Research or delegate when evidence is needed.
Update backlog, sprint, decisions, evidence, conflicts, and task files.
Stop before implementation.

Required Reading

• Always read references/workflow.md before acting.
• Read references/gates.md before asking founder questions, running research, changing sprint/backlog state, or declaring a task ready.
• Read references/planning-contract.md before creating or updating planning artifacts, sprint trackers, backlog rows, or task files.
• Read references/decomposition.md before splitting a feature, planning a wide refactor, or deciding whether discovery is too foggy for a task graph.
• Read references/research-and-delegation.md only when web research, public-evidence claims, technical feasibility review, conflict review, or subagent delegation triggers apply.
• Read ../build-right-engineering-principles/references/principles.md when splitting features into implementation tasks, selecting technologies, planning architecture, storage, integration, deployment, service-boundary, or package changes, designing contracts, changing provider boundaries, or planning security, reliability, observability, or test strategy.
• Use assets/templates/tasks/feature-task.md when creating a new execution task.
• Use assets/templates/tasks/post-release-backlog.md when creating a missing backlog tracker.
• Use bundled scripts/feature-planning-check.ts for deterministic planning surface, gate, destination, and task-candidate signals. Treat script output as input to judgment, not authority.
• Use bundled scripts/ensure-openspec.ts before planning. Managed setup is internal and idempotent; never route provider setup or commands to the user.
• Use bundled scripts/openspec-change-check.ts after Build Right planning gates clear. It is the only feature-planning entrypoint for managed change creation, dependency-ordered artifact state, strict validation, and thin task binding.
• Invoke every managed helper used as evidence as its own direct Bun shell command. Do not chain it with &&, ;, pipes, redirects, or trailing commands; the native evidence gate binds success to that isolated invocation.