[Extension]: Add guildwork (request, verdict, register) #5210

Extension ID

guildwork

Extension Name

Guildwork: request, verdict, register

Version

0.1.0

Description

No code is written until a named human approves a written request, and every verdict is kept.

Author

Simon Dupont (@Simon-Pacifae-Dupont)

Repository URL

https://github.com/Simon-Pacifae-Dupont/Guildwork

Download URL

https://github.com/Simon-Pacifae-Dupont/Guildwork/releases/download/guildwork-v0.1.0/guildwork.zip

License

MIT

Homepage (optional)

https://github.com/Simon-Pacifae-Dupont/Guildwork/tree/main/integrations/spec-kit

Documentation URL (optional)

https://github.com/Simon-Pacifae-Dupont/Guildwork/blob/main/integrations/spec-kit/README.md

Changelog URL (optional)

https://github.com/Simon-Pacifae-Dupont/Guildwork/blob/main/integrations/spec-kit/CHANGELOG.md

Required Spec Kit Version

=1.0.0

Required Tools (optional)

None.

Number of Commands

4

Number of Hooks (optional)

3

Tags

governance, human-in-the-loop, approval, audit-trail, multi-agent

Key Features

• After /speckit.tasks, writes one request a named person rules on: objective, acceptance criteria, scope, out of scope, stop conditions, risk, who decides, and the SHA-256 of spec, plan and tasks.
• The verdict is typed by that person: approved, held <what must change> or refused <why>. A reason is required for the last two; nothing else counts as a verdict.
• A mandatory before_implement gate that reads only, refuses on the first of seven conditions and names it, including a spec, plan or tasks changed after the verdict.
• after_implement, the run closes on delivered, partial or stopped, criterion by criterion with evidence.
• Every verdict and close is appended to .specify/memory/guildwork-register.md, never edited, and kept when the extension is removed.

Testing Checklist

• Extension installs successfully via download URL
• All commands execute without errors
• Documentation is complete and accurate
• No security vulnerabilities identified
• Tested on at least one real project

Submission Requirements

• Valid extension.yml manifest included
• README.md with installation and usage instructions
• LICENSE file included
• GitHub release created with version tag
• All command files exist and are properly formatted
• Extension ID follows naming conventions (lowercase-with-hyphens)

Testing Details

Tested on: Linux, Spec Kit 1.2.6.dev0 (main @ 7370e59), Claude integration (skills layout).

Test project: a throwaway Spec Kit project (specify init --integration claude) with one fictional feature, specs/001-stale-tiles (spec, plan, tasks).

Test scenarios:

1. specify extension add guildwork --from <download URL>: installed, 4 skills registered, 3 hooks written to .specify/extensions.yml (before_implement with optional: false), command tokens and script paths rendered.
2. Gate with no request: refused, condition 1. Request written from the template: no placeholder left.
3. Gate with the request pending: condition 3. Verdict ok: not recorded. held without a reason: not recorded. held <reason>: recorded; gate refuses on condition 4 with the reason.
4. approved: gate opens, naming who approved and when.
5. plan.md edited after approval: gate refuses on condition 7 naming plan; a verdict on the stale request is not recorded. Request rewritten, verdict back to pending (condition 3).
6. refused <reason>: condition 5. Placeholder in Who decides: condition 2. Verdict: done or an empty By: condition 6.
7. Close: partial, 2 of 3 criteria met with evidence, the unmet one sent to a new request. Register holds every verdict and the close.
8. specify extension remove guildwork --force: skills removed, register kept.

Example Usage

specify extension add guildwork --from https://github.com/Simon-Pacifae-Dupont/Guildwork/releases/download/guildwork-v0.1.0/guildwork.zip

/speckit.tasks                       # accept the offer: /speckit.guildwork.request writes the request
/speckit.guildwork.verdict approved  # typed by the person named under "Who decides"
/speckit.implement                   # the gate opens; it refuses again if spec, plan or tasks change

Proposed Catalog Entry

{
  "guildwork": {
    "name": "Guildwork: request, verdict, register",
    "id": "guildwork",
    "description": "No code is written until a named human approves a written request, and every verdict is kept.",
    "author": "Simon Dupont (@Simon-Pacifae-Dupont)",
    "version": "0.1.0",
    "download_url": "https://github.com/Simon-Pacifae-Dupont/Guildwork/releases/download/guildwork-v0.1.0/guildwork.zip",
    "sha256": "f5793fe480f3a607cdab0debe483e8f3a7aa936fff4efec7200f728d5023bd72",
    "repository": "https://github.com/Simon-Pacifae-Dupont/Guildwork",
    "homepage": "https://github.com/Simon-Pacifae-Dupont/Guildwork/tree/main/integrations/spec-kit",
    "documentation": "https://github.com/Simon-Pacifae-Dupont/Guildwork/blob/main/integrations/spec-kit/README.md",
    "changelog": "https://github.com/Simon-Pacifae-Dupont/Guildwork/blob/main/integrations/spec-kit/CHANGELOG.md",
    "license": "MIT",
    "category": "process",
    "effect": "read-write",
    "requires": {
      "speckit_version": ">=1.0.0"
    },
    "provides": {
      "commands": 4,
      "hooks": 3
    },
    "tags": ["governance", "human-in-the-loop", "approval", "audit-trail", "multi-agent"],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-11-02T00:00:00Z",
    "updated_at": "2026-11-02T00:00:00Z"
  }
}

Additional Context

The extension lives in a subfolder of the Guildwork repository (integrations/spec-kit/), with a release asset whose root holds extension.yml, the same layout as other catalog entries published from a larger repository. Guildwork is an open governance kit for running several AI coding agents on one repository; this extension carries only its request, verdict and register, and does not replace any core command.