featureplan-kickoff
Skill63 starsChanged 4 days agoMITView on GitHub
VNX 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).
In this repository56 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .claude/terminals/T0/CLAUDE.mdCLAUDE.md
- .claude/terminals/T1/CLAUDE.mdCLAUDE.md
- .claude/terminals/T2/CLAUDE.mdCLAUDE.md
- .claude/terminals/T3/CLAUDE.mdCLAUDE.md
- api-developerSkill
- architectSkill
- backend-developerSkill
- control-centreSkill
- data-analystSkill
- database-engineerSkill
- debuggerSkill
- excel-reporterSkill
- fabric-referenceSkill
- frontend-developerSkill
- horizonSkill
- intelligence-engineerSkill
- monitoring-specialistSkill
- panelSkill
- performance-profilerSkill
- plannerSkill
- pmSkill
- python-optimizerSkill
- quality-engineerSkill
- refactor-safeSkill
- reviewerSkill
- security-engineerSkill
- supabase-expertSkill
- t0-orchestratorSkill
- test-engineerSkill
- vnx-managerSkill
- api-developerSkill
- architectSkill
- backend-developerSkill
- data-analystSkill
- database-engineerSkill
- debuggerSkill
- excel-reporterSkill
- fabric-referenceSkill
- featureplan-kickoffSkill
- frontend-developerSkill
- horizonSkill
- intelligence-engineerSkill
- monitoring-specialistSkill
- performance-profilerSkill
- plannerSkill
- pmSkill
- python-optimizerSkill
- quality-engineerSkill
- refactor-safeSkill
- reviewerSkill
- security-engineerSkill
- supabase-expertSkill
- t0-orchestratorSkill
- test-engineerSkill
- vnx-managerSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
27 rules. About 0 are common, 15 are distinctive, and 12 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈15
Distinctive · estimate
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 44
Use root FEATURE_PLAN.md as the active feature source of truth.
- Very specific: line 45
Use vnx horizon queue (alias vnx objective queue) as the queue surface and the dispatch register as the truth behind it.
- Distinctive: line 47
Use CLI and state verification.
- Distinctive: line 48
Do not promote more than one new dispatch during kickoff.
- Very specific: line 49
If kickoff preconditions are contradictory or unsafe, stop and report WAIT or ESCALATE.
- Very specific: line 50
When kickoff succeeds, explicitly tell the operator or T0 to resume per role-orchestrator.md's Mandatory Startup …
- Distinctive: line 56
Treat these conventions as deterministic requirements, not suggestions.
- Very specific: line 70
Use @skill-name in plan metadata and human-readable feature documents
- Very specific: line 71
Use /skill-name only as the literal in-terminal command syntax when a worker must manually load a skill in an interactive session
- Very specific: line 72
Never write /skill-name inside FEATURE_PLAN.md
- Very specific: line 73
Never convert an invalid @skill-name into a guessed /skill-name at kickoff time
- Distinctive: line 77
Use exact field shape:
- Distinctive: line 85
If present, review metadata must use:
- Distinctive: line 97
Do not silently coerce malformed metadata into a guessed valid value during kickoff
- Distinctive: line 101
Run these steps in order.
- Very specific: line 115
every Skill: value maps to a real installed skill or documented alias
- Distinctive: line 135
If the worktree or queue is clearly unsafe, stop and explain exactly why.
- Distinctive: line 140
prefer the earliest PR with no unmet dependencies
- Distinctive: line 141
if the kickoff request names a specific PR, validate that it is actually promoteable
- Very specific: line 142
do not promote a sibling PR just because it also has no dependencies if the plan clearly wants PR-0 first
- Very specific: line 163
Only if validation passes.
- Distinctive: line 171
Never promote a second dispatch during kickoff.
- Distinctive: line 192
Do not continue silently if:
- Distinctive: line 194
no PR sections can be found
- Distinctive: line 206
do not promote anything
- Distinctive: line 216
Use the canonical feature-plan example as the structural baseline for:
- Very specific: line 224
If the active FEATURE_PLAN.md deviates materially from that shape, stop before promotion and report the exact mismatch.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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-listClassify:
- 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

