# Build Feature

> Delivers a new rocprof-compute feature end-to-end in one owner: aggregate Jira intake, questionnaire and formulation, approved low-level design, approved graph plan, package RED/test-blind GREEN, deterministic restacking, final integration, one terminal review, and verified stacked PR publication. Use for new-feature or full-delivery intent, plan-and-implement, literal `$build-feature`, or exact resume of active build-feature state. Human-invoked only.

- Skill: `abchoudh-amd/build-feature` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add abchoudh-amd/build-feature`
- Raw SKILL.md: https://api.skillmd.com/api/skills/abchoudh-amd/build-feature/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: abchoudh-amd (https://skillmd.com/u/abchoudh-amd)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/abchoudh-amd/build-feature

---


# Build Feature

Own one umbrella run from Jira intake through verified stacked publication. Consume the
shared planning and implementation contracts directly; never invoke or transfer ownership
to the public `plan-feature` or `implement-feature` skills.

## Required contracts

Before acting, read:

- [`FEATURE-WORKFLOW-ROUTING.md`](../_shared/FEATURE-WORKFLOW-ROUTING.md);
- [`FEATURE-WORKFLOW-STATE.md`](../_shared/FEATURE-WORKFLOW-STATE.md);
- [`FEATURE-PLANNING-CONTRACT.md`](../_shared/FEATURE-PLANNING-CONTRACT.md); and
- [`FEATURE-IMPLEMENTATION-CONTRACT.md`](../_shared/FEATURE-IMPLEMENTATION-CONTRACT.md).

Also follow runtime-local problem-definition, low-level-design, planner, approved-plan,
boundary, review, worktree, and PR contracts.

## Entry and ownership

Initialize new full-delivery work with one or more supplied Jira keys and
`init --owner build-feature`. Resume only one exact active umbrella state path. An exact
approved plan may be bound directly; an exact released planning state may be `claim`ed only
by an explicit user request. The recorded owner remains `build-feature` through completion
and every plan revision.

Never scan for newest state, create an atomic no-plan bypass, or nest public feature skills.
Enter only on a direct human request under the routing contract's human front door; refuse
invocation by a spawned agent or another skill.

## Planning half

Close one maximum-50 supplied-plus-context Jira snapshot closure; create one aggregate
questionnaire and formulation, the formulation approved in plan mode before it is
published; author one low-level design through `rocprof-compute-lld-writer`, its questions
resolved through `grill-me`, its exact bytes approved before publication, and its path and
digest recorded with `set-lld` before any planner dispatch; handle planner questions
through `grill-me`; require a parser-valid 1–9 package DAG of thin vertical slices, each
behavior delivered by one package, interface contracts copied unchanged from the approved
design with one provider per name, an optional first `kind: "interface"` package, and
final integration and stack publication; display exact pending bytes; obtain explicit
approval; and publish receipt-bound plan bytes. Retain umbrella ownership at `plan_ready`
and enter implementation.

## Implementation half

Schedule only dependency-ready stable `WPn` packages, one lane at a time in the returned
longest-gated-chain order, since Cursor admits exactly one live controlled claim and
ordering alone decides elapsed time. Each runs genuine package RED,
verbatim package blind GREEN, independent gate, `phase-review` audit, and one checkpoint.
Restack every non-final package deterministically, run the final-integration package at the
assembled tip (including final-only unit/CLI/docs/changelog ownership), run one aggregate
gate, and perform one terminal review. Passing terminal gates proceed through recorded GitHub
preflight, verified pushes, draft stacked PRs, deterministic links, exact title-bound views,
and create-pr `resume` recovery for a surfaced but unrecorded successful create; gate
failure completes without remote publication.

Before terminal review, a plan defect keeps owner `build-feature` and returns this state to
planning for a distinct freshly approved graph. Test evidence still never enters planning
artifacts or blind source payloads.

## Response

At a human pause return the exact state path, its stage, the artifact, and the resume
action. At completion
return exact Jira/plan/state identities, stable package evidence and commits, restack map,
blindness attestation, final gate, exact review body/path, residual risks, and ordered
verified stacked-PR map or exact no-publication reason.

## Resources

- [REFERENCE.md](REFERENCE.md) — umbrella, DAG, plan-revision, and publication invariants.
- [EXAMPLES.md](EXAMPLES.md) — full delivery, cross-runtime resume, and terminal outcomes.
- [writing style](../_shared/WRITING-STYLE.md) — normative prose rules and the pre-save self-check for
  every human-read artifact this skill produces.