Run any Skill in Manus with one click

forgemyspec-implement

Stars7

Forks0

UpdatedApril 17, 2026 at 02:11

Implements work strictly from an existing ForgeMySpec bundle (spec.yaml, CLAUDE.md, acceptance checklist). Use when the spec is already written and the user wants coding execution without re-compiling the requirement. Combines well with MCP tools for reading tests, CI, and repo structure during implementation.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ferrarimarlon

ferrarimarlon/ForgeMySpec

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	forgemyspec-implement
description	Implements work strictly from an existing ForgeMySpec bundle (spec.yaml, CLAUDE.md, acceptance checklist). Use when the spec is already written and the user wants coding execution without re-compiling the requirement. Combines well with MCP tools for reading tests, CI, and repo structure during implementation.

Implement from ForgeMySpec bundle

Preconditions

spec.yaml exists and is the source of truth.
Supporting files present as generated by ForgeMySpec: CLAUDE.md, acceptance-checklist.md, and optionally .claude/commands/implement-from-spec.md.

Steps

Read spec.yaml (objective, constraints, hypotheses, actions, success criteria, required evidence).
Follow actions in a sensible order; honor supports links to hypotheses.
Satisfy required_evidence with concrete artifacts (test runs, command output).
Complete acceptance-checklist.md honestly.
Update CLAUDE.md only with stable decisions and pitfalls—not scratch logs.

MCPs

Use MCPs to verify integrations, run tests, or fetch live data needed for evidence. Do not expand product scope beyond the spec unless the user explicitly revises spec.yaml.

Reference

See ../forgemyspec/references/implement-from-spec-workflow.md in this repository for the full handoff narrative.

More from this repository

same repository

forgemyspec-amend

ferrarimarlon/ForgeMySpec

Safely amends an existing ForgeMySpec spec.yaml in response to new information discovered during implementation (wrong assumption, tightened constraint, scope change). Proposes only the minimal delta, validates the result with lint, and shows a diff before writing. Never rewrites the whole spec without explicit user approval.

2026-04-307

forgemyspec

ferrarimarlon/ForgeMySpec

Compiles a human requirement into a validated operational spec (spec.yaml) and Claude execution artifacts (CLAUDE.md, acceptance checklist, implement command, scope eval seeds). Use when the user wants spec-driven development, a concrete execution contract before coding, or to reduce scope drift. Prefer this skill inside Claude Code where MCP tools can supply repository, docs, or ticket context before drafting the spec.

2026-04-307

name	forgemyspec-implement
description	Implements work strictly from an existing ForgeMySpec bundle (spec.yaml, CLAUDE.md, acceptance checklist). Use when the spec is already written and the user wants coding execution without re-compiling the requirement. Combines well with MCP tools for reading tests, CI, and repo structure during implementation.

Implement from ForgeMySpec bundle

Preconditions

spec.yaml exists and is the source of truth.
Supporting files present as generated by ForgeMySpec: CLAUDE.md, acceptance-checklist.md, and optionally .claude/commands/implement-from-spec.md.

Steps

Read spec.yaml (objective, constraints, hypotheses, actions, success criteria, required evidence).
Follow actions in a sensible order; honor supports links to hypotheses.
Satisfy required_evidence with concrete artifacts (test runs, command output).
Complete acceptance-checklist.md honestly.
Update CLAUDE.md only with stable decisions and pitfalls—not scratch logs.

MCPs

Use MCPs to verify integrations, run tests, or fetch live data needed for evidence. Do not expand product scope beyond the spec unless the user explicitly revises spec.yaml.

Reference

See ../forgemyspec/references/implement-from-spec-workflow.md in this repository for the full handoff narrative.