Spec execute next
Skill ainova-systems/intelligence-dev-packs/packs/spec/skills/spec-execute-next
Intelligence pack for software engineering based on Ainova Systems best practices
npx -y skills add ainova-systems/intelligence-dev-packs --skill spec-execute-nextAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Autonomously pick the highest-value ready spec, drive it to an outcome-labeled PR, reset the workspace
SKILL.md
3.0 KB, as published. Nobody here has run it
Execute Next Best Task
Orchestrator-of-orchestrators: select ONE ready item, delegate the whole execution to spec-execute / spec-continue (their rules apply verbatim - this skill adds only selection and cleanup), then reset the workspace. Designed for autonomous and scheduled runs.
Steps
- Preflight.
git status --porcelainclean (dirty - halt and surface; never sweep foreign work into a task).git switch <base> && git pull && git fetch --prune. - Inventory.
- Candidates:
approvedspecs in the project's spec area (profilespecs_dir; else detect) - the primary pool - plusin-progressspecs with no open PR (to finish; finishing beats starting). Neverproposed(unreviewed - the owner approves viaspec-approvefirst),completed,cancelled, orsuperseded. Skip idea-collection notes without a concrete ticket-sized item. - In-flight work:
gh pr list --state open --json number,title,headRefName,labels,updatedAt; per-PR file scope viagh pr view <n> --json files --jq '.files[].path'.
- Candidates:
- Select ONE.
- Value order: explicit priority marker - mid-flight spec with no open PR (finishing beats starting) - unblocks queued work - smaller effort at equal value. A focus-hint argument narrows the pool, never overrides the conflict gate.
- Conflict gate, skip the candidate if: it already has an open PR (
ai:manual/ai:failedPRs need the owner, not a re-run); its file scope overlaps any open PR's files; it needs a decision the spec leaves open (that isai:manualbefore even starting). - Interactive session - confirm the choice plus runner-up in one question. Autonomous run - proceed. No eligible candidate - report per-candidate skip reasons and stop (skip step 5's sync, still end clean).
- Execute until outcome. Mid-flight spec -
spec-continue; otherwisespec-execute. Run until the PR carries exactly oneai:*label. Never merge. - Reset (runs regardless of outcome).
git switch <base> && git pull && git fetch --prune. Close any spec whose PR merged since the last run (spec-close) so the queue and docs reflect reality. Re-sync intelligence outputs when the project uses intelligence-sync (bash <umbrella>/sync/scripts/sync.sh). Report: task picked + why; PR URL + outcome label; what needs the owner; runner-up for the next run.
Verify
- Exactly one task progressed to an outcome label; workspace back on a clean, current base.
Scope / hand-off
- All execution rules -
spec-execute; the merge -git-merge-prafter owner accept. The approved queue this skill drains is filled byspec-approve(the owner's gate-1 decision).
CRITICAL
- ONE task per invocation; the next starts only after reset and fresh context.
- The conflict gate is non-negotiable - when in doubt about overlap, pick the next candidate.
- Never block other agents' open PRs.