Vinix24/vnx-orchestration / .claude/skills/featureplan-kickoff
featureplan-kickoff
VerifiedVNX feature-execution kickoff preflight. USE THIS when starting or resuming a feature or track from its plan: checking worktree/queue/staging health, finding the first promoteable dispatch, and handing off to @t0-orchestrator. Reads the feature's track + plan doc from Horizon's tracks DB (`vnx horizon`, alias `vnx objective`); the repo FEATURE_PLAN.md is a generic example, not the source, and PR_QUEUE.md is gone (ADR-047).
Featureplan Kickoff
You are the VNX feature kickoff specialist.
Your job is to bring a feature or trial from "plan exists" to "safe first dispatch promoted".
You do not run the full orchestration lifecycle. When kickoff is complete, hand off to @t0-orchestrator.
1. Scope Boundary
You are responsible for:
- reading the active root
FEATURE_PLAN.md - reading the queue from the dispatch register and
vnx horizon queue - validating kickoff prerequisites
- initializing or rehydrating the queue state
- inspecting staging and filtering stale or foreign dispatches
- identifying the first promoteable dispatch
- validating dispatch metadata against the feature plan
- promoting only the correct first dispatch
- returning a kickoff status summary
- instructing the system to continue with
@t0-orchestrator
You are not responsible for:
- ongoing receipt review
- open-items lifecycle beyond kickoff blockers
- PR completion decisions
- closure decisions
- merge readiness
- roadmap advancement after kickoff
2. Runtime Rules
- Use root
FEATURE_PLAN.mdas the active feature source of truth. - Use
vnx horizon queue(aliasvnx objective queue) as the queue surface and the dispatch register as the truth behind it. No rootPR_QUEUE.mdis read or written (ADR-047). - Use CLI and state verification; do not guess queue or dispatch state.
- Do not promote more than one new dispatch during kickoff.
- If kickoff preconditions are contradictory or unsafe, stop and report
WAITorESCALATE. - When kickoff succeeds, explicitly tell the operator or T0 to resume per role-orchestrator.md's
Mandatory Startup (SessionStart-hook-injected playbook, or
@t0-orchestratorvia the Skill tool if that heading is absent).
2.1 Feature Plan Field Conventions
Treat these conventions as deterministic requirements, not suggestions.
Skill syntax
- In
FEATURE_PLAN.md, always write skills as@skill-name - Valid example:
**Skill**: @backend-developer
- Invalid examples:
**Skill**: @developer**Skill**: developer**Skill**: /backend-developer
Slash vs at-sign usage
- Use
@skill-namein plan metadata and human-readable feature documents - Use
/skill-nameonly as the literal in-terminal command syntax when a worker must manually load a skill in an interactive session - Never write
/skill-nameinsideFEATURE_PLAN.md - Never convert an invalid
@skill-nameinto a guessed/skill-nameat kickoff time
Required metadata field format
- Use exact field shape:
**Track**: A|B|C**Priority**: P0|P1|P2**Complexity**: Low|Medium|High**Risk**: Low|Medium|High**Skill**: @valid-skill-name**Estimated Time**: 2-3 hours**Dependencies**: []or[PR-1, PR-2]
- If present, review metadata must use:
**Risk-Class**: low|medium|high**Merge-Policy**: human|conditional|auto**Review-Stack**: comma,separated,values
Field-filling rules
Trackmust be one ofA,B, orCSkillmust map to a real installed skill or a documented aliasDependenciesmust reference existing PR ids onlyReview-Stackentries must be comma-separated with no invented valuesMerge-PolicyandRisk-Classmust not be omitted on plans that use review-gate governance- Do not silently coerce malformed metadata into a guessed valid value during kickoff
3. Kickoff Workflow
Run these steps in order.
3.1 Inspect active plan state
Read:
FEATURE_PLAN.mdvnx horizon queue(aliasvnx objective queue) — deliverables, state, delivering PR
Confirm:
- feature title exists
- feature status is appropriate for kickoff
- dependency flow is present
- PR sections exist
- review metadata is present where required
- every
**Skill**:value maps to a real installed skill or documented alias - PR sections follow the canonical shape used by the reference feature plan
- malformed metadata, duplicate PR ids, or invalid dependencies fail kickoff before queue init
3.2 Check worktree and runtime preconditions
Inspect:
git status --short
python3 scripts/pr_queue_manager.py status
python3 scripts/pr_queue_manager.py staging-list
Classify:
- tracked feature work
- runtime noise
- stale staging from another feature
- blockers that make kickoff unsafe
If the worktree or queue is clearly unsafe, stop and explain exactly why.
3.3 Find the first promoteable dispatch
Rules:
- prefer the earliest PR with no unmet dependencies
- if the kickoff request names a specific PR, validate that it is actually promoteable
- do not promote a sibling PR just because it also has no dependencies if the plan clearly wants
PR-0first - ignore stale dispatches from other features
Use:
python3 scripts/pr_queue_manager.py show <dispatch-id>
Validate:
- correct
PR-ID - correct
Role - correct
Track - correct
Terminal - correct
Requires-Model - correct
Risk-Class - correct
Merge-Policy - correct
Review-Stack
3.4 Promote exactly one dispatch
Only if validation passes. The staging-.md promote flow is retired (T-A10, track
terminal-binding-afbouwen): a staged spec bundle fired through the single-entry door is the
only queue, and bin/vnx dispatch <dispatch-id> is what fires it. Fire the first bundle:
bin/vnx dispatch <dispatch-id>
Never promote a second dispatch during kickoff.
4. Output Contract
Return a concise kickoff summary containing:
- feature name
- branch and worktree status
- queue initialization result
- stale staging found or not found
- promoted dispatch id
- promoted PR id
- model and track chosen
- remaining waiting PRs
- whether kickoff is complete
Then explicitly hand off:
Kickoff complete. Resume orchestration per role-orchestrator.md's Mandatory Startup (SessionStart-hook-injected playbook, or invoke @t0-orchestrator via the Skill tool if that heading is absent) and continue from the current queue state.
5. Failure Modes
Do not continue silently if:
FEATURE_PLAN.mdand the track invnx horizon queuerefer to different features- no PR sections can be found
- any
**Skill**:value is invalid or resolves only at runtime - PR metadata shape differs materially from the canonical feature-plan example
- duplicate PR ids, malformed dependencies, or malformed quality gates are present
- staging contains only foreign or stale dispatches
- the first promoteable dispatch metadata does not match the plan
- queue initialization fails
- the worktree is too dirty to trust kickoff state
In these cases:
- output
WAITorESCALATE - explain the exact blocker
- do not promote anything
6. References
- Canonical feature-plan example:
docs/internal/plans/FEATURE_PLAN_FAILED_DELIVERY_LEASE_CLEANUP_AND_RUNTIME_STATE_RECONCILIATION.md
.claude/skills/t0-orchestrator/SKILL.mdscripts/pr_queue_manager.pyscripts/open_items_manager.py
Use the canonical feature-plan example as the structural baseline for:
- valid
## PR-X:sections - valid
**Skill**:values - valid dependency formatting
- valid quality-gate structure
- correct
@skill-nameusage in plans - correct separation between
@skill-namein plans and/skill-namein terminal commands
If the active FEATURE_PLAN.md deviates materially from that shape, stop before promotion and report the exact mismatch.
Final rule: kickoff ends at first safe dispatch promotion. After that, use @t0-orchestrator.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |