speckit-workforce-approve

Records human approval decisions for assembled agent rosters in spec-driven development pipelines.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/NarenKarthikBM/specseyal --skill speckit-workforce-approve-narenkarthikbm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-workforce-approve
Source: https://github.com/NarenKarthikBM/specseyal/tree/main/.claude/skills/speckit-workforce-approve
Command: npx skills add https://github.com/NarenKarthikBM/specseyal --skill speckit-workforce-approve-narenkarthikbm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In a spec-driven development pipeline, tasks are categorized and assigned to specialized parallel agents before implementation begins. Without a human checkpoint, a flawed or over-privileged agent roster could consume tokens and execute code changes unchecked. This Skill provides the workforce human gate: it records a reviewer's decision on the assembled agent roster and unlocks parallel implementation only after explicit approval. ## Core Features & Use Cases - Roster Review Presentation: Displays the assembled agent roster table (base, model, skills, elevated grants) alongside tasks.md so a human can verify assignments before implementation. - Decision Recording: Resolves the six gate fields (timestamp, reviewer, decision, reviewed, notes, overrides) in agents/assignment.md, appending a new block for corrections rather than editing history. - Grant Tripwire Enforcement: Forces human review whenever any agent carries elevated grants (e.g., web_search), even when the profile is set to auto mode. - Gate Hook Firing: On approval, triggers the git extension's on-gate-approve.sh to bind artifact SHAs into gates.yml, unlocking /speckit-implement-parallel. - Use Case: After running /speckit-categorize and /speckit-agent-assign for a feature, a reviewer runs this command with 'approved' to sign off the roster, or 'rejected' with notes to send it back for reassignment. ## Quick Start Run /speckit-workforce-approve approved after reviewing the agent roster in agents/assignment.md to record your approval and unlock parallel implementation.

Frequently Asked Questions about speckit-workforce-approve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I approve an agent roster before parallel implementation?

Run /speckit-workforce-approve with a decision of approved, approved-with-notes, or rejected, optionally followed by free-text notes. The command records the decision in the Workforce Gate section of agents/assignment.md and, on approval, fires the hook that unlocks /speckit-implement-parallel.

What must run before the workforce approval gate?

Run /speckit-categorize first, then /speckit-agent-assign, which produces agents/assignment.md containing the Workforce Gate section and Roster approved table. If that file or section is missing, the command stops with an error naming the missing prerequisite.

Can the workforce gate run automatically without a human?

Yes, when profile.yaml sets gates.workforce.mode to auto, /speckit-agent-assign writes the gate section itself. However, any elevated grant in the roster forces human mode regardless of profile, since approving grants means approving network or tool access.

What happens when a roster is rejected at the workforce gate?

On rejection, no approval hook fires and nothing is unlocked. The roster returns for reassignment: /speckit-agent-assign re-runs, typically after the concern in the notes is addressed, producing a fresh assignment.md with a new pending gate.

Why does the workforce gate write no traces.jsonl record?

The gate runs no LLM session — a human reads the roster and decides — so there are no role, model, token, or duration values to report. The audit trail lives in the Workforce Gate section itself and the gates.yml binding written on approval.