agentsclimarketplace

Implement

Skill pooyagolchian/specforge/plugins/specforge/skills/implement

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 implement

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

Execute the approved task list to build the feature — the guarded build phase. Use when the user explicitly wants to implement, build, or write the code for a feature whose spec and plan are approved. Code edits are blocked by the SpecForge gate until spec + plan are approved; this skill runs the tasks in order and keeps state in sync.

SKILL.md

2.4 KB, as published. Nobody here has run it

/specforge:implement — build it, under the gate

Execute tasks.md top-to-bottom to implement the active feature. This is deliberately user-invoked only (not auto-triggered) so building is an explicit decision. The PreToolUse gate will refuse code edits unless the feature's specify and plan are approved — so if you haven't approved yet, do that first.

When to use

  • The user explicitly asks to implement/build the feature.
  • Trigger: /specforge:implement.

Preconditions (checked first)

  1. There is an active feature in specforge/state.md.
  2. Its specify and plan rows read approved. If not, stop and tell the user to run /specforge:approve specify and /specforge:approve plan (or /specforge:quick for a trivial change). Do not attempt to edit code before this — the gate will block it anyway.

Steps

  1. Read the active feature's plan.md, tasks.md, data-model.md, and contracts/.
  2. Work tasks in order, honoring [P] groupings where safe. Prefer the tests-first tasks before their implementation tasks.
  3. As each task completes, check its box in tasks.md ([ ] → [x]). Keep the file as the live progress record so /specforge:resume can pick up after a context reset.
  4. If you discover the design is wrong, do not silently hack around it — stop, update the plan/spec first (or tell the user), then regenerate tasks. Docs stay the source of truth.
  5. When all tasks are done: run the feature's quickstart.md steps (or tests) to verify, update specforge/state.md (| NNN-slug | implement | done | <date> |), and append an audit row.
  6. Summarize what was built, what was verified, and any follow-ups.

Guardrails

  • Stay within the scope of tasks.md. New scope means a new spec/plan cycle, not ad-hoc edits.
  • Never edit generated code to "fix" a design flaw without updating the design — that is how specs and code drift apart.
  • If the gate blocks an edit, that is working as intended: finish approvals or fast-track.

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.