Run any Skill in Manus with one click

opforge-spec-authoring

Stars5

Forks1

UpdatedMay 13, 2026 at 18:27

Write implementation-ready opForge specifications with explicit goals, non-goals, invariants, acceptance criteria, and validation expectations. Use when behavior needs to be designed before planning or coding begins.

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

pig-games

pig-games/opForge

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	opforge-spec-authoring
description	Write implementation-ready opForge specifications with explicit goals, non-goals, invariants, acceptance criteria, and validation expectations. Use when behavior needs to be designed before planning or coding begins.

opForge Spec Authoring

Use when

behavior needs design before planning or coding
scope, invariants, or acceptance criteria are unclear
later plan derivation should be mechanical

Required output

Use templates/spec-template.md without changing its validator-facing headings.

A valid spec states:

summary, problem, goals, non-goals, invariants, behavioral contract, boundary cases, acceptance criteria, validation expectations, and open questions
checkbox goals and checkbox acceptance criteria
unresolved decisions explicitly, without hidden assumptions

Guardrails

Non-goals are mandatory.
Acceptance criteria must be concrete and testable.
Do not smuggle implementation plans into the spec.
Do not broaden scope beyond the user request.

Validate with

scripts/workflow/check_workflow_artifact_bundle.py
scripts/workflow/run_spec_workflow.sh

More from this repository

same repository

opforge-plan-authoring

pig-games/opForge

Create execution-ready opForge plans from specs, reviews, or explicitly scoped user requests. Use when implementation or remediation work needs ordered, commit-sized slices with checkboxes, validations, and definition-of-done rules.

2026-05-135

opforge-review-closure

pig-games/opForge

Verify and document that claimed review fixes actually close the original opForge findings. Use when remediation work claims to resolve prior review items and closure evidence must be recorded.

2026-05-135

opforge-review-reporting

pig-games/opForge

Create normalized opForge review reports with findings-first structure, stable finding IDs, evidence-based severity, and explicit testing gaps. Use when a code review needs to be written, cleaned up, or merged from multiple reviewers.

2026-05-135

name	opforge-spec-authoring
description	Write implementation-ready opForge specifications with explicit goals, non-goals, invariants, acceptance criteria, and validation expectations. Use when behavior needs to be designed before planning or coding begins.

opForge Spec Authoring

Use when

behavior needs design before planning or coding
scope, invariants, or acceptance criteria are unclear
later plan derivation should be mechanical

Required output

Use templates/spec-template.md without changing its validator-facing headings.

A valid spec states:

summary, problem, goals, non-goals, invariants, behavioral contract, boundary cases, acceptance criteria, validation expectations, and open questions
checkbox goals and checkbox acceptance criteria
unresolved decisions explicitly, without hidden assumptions

Guardrails

Non-goals are mandatory.
Acceptance criteria must be concrete and testable.
Do not smuggle implementation plans into the spec.
Do not broaden scope beyond the user request.

Validate with

scripts/workflow/check_workflow_artifact_bundle.py
scripts/workflow/run_spec_workflow.sh