agentsclimarketplace

Approve

Skill pooyagolchian/specforge/plugins/specforge/skills/approve

Spec-driven AI development lifecycle for Claude Code — spec-kit + AI-DLC fused, with hook-enforced human-approval gates. Installable plugin + marketplace.

Install
npx -y skills add pooyagolchian/specforge --skill approve

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 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

Record human approval of a lifecycle stage (specify, plan, tasks, analyze) for the active feature. Use when the user says they approve the spec/plan, want to sign off a stage, or unblock implementation. Flips the stage to approved in specforge/state.md — approving both specify and plan is what opens the code-edit gate.

SKILL.md

2.0 KB, as published. Nobody here has run it

/specforge:approve — sign off a gate

Record a human's approval of a stage. Approvals are deliberate human acts — this skill is user-invoked only and never auto-triggers. Approving both specify and plan for the active feature is what unblocks code edits (the PreToolUse gate).

Usage

/specforge:approve <stage> where <stage> ∈ {specify, plan, tasks, analyze}. If no stage is given, approve the furthest-completed unapproved stage, or ask which one.

Steps

  1. Confirm the active feature from specforge/state.md (<!-- active: … -->).
  2. Confirm the artifact for that stage exists and the user has actually reviewed it. Briefly restate what they're approving (e.g. "Approving the plan for 001-todo-crud — architecture, tech decisions, and traceability."). Do not approve on the user's behalf without their say-so.
  3. In specforge/state.md, set that stage's row to approved with today's date: | NNN-slug | <stage> | approved | <date> | (add the row if missing).
  4. Audit: append | <today ISO-8601> | NNN-slug | approve | <stage> approved by user |.
  5. Report the new gate status:
    • If both specify and plan are now approved → tell the user code edits are unblocked and they can run /specforge:implement.
    • Otherwise → say what still needs approval.

Guardrails

  • Approval means a human reviewed it. If the user just says "approve everything", confirm they've read the artifacts first.
  • Never edit application code from this skill — it only updates state.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.