forge-spec
Skill13 starsChanged 44 days agoMITView on GitHub
Define product, experience, and contract intent using deliberate Project or Issue templates. Use for "Forge spec", asking Forge to specify or scope a feature, or a caller-selected Spec phase. Produces a proposal and boundary check; does not authorize Build, canonical Spec writes, or publication.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- DailenG/forge-workflowtheir own version, first seen Jul 25, 2026
- tonmoy007/forge-pluginstheir own version, first seen Jun 9, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- tonmoy007/forge-plugins★ 2same name
- DailenG/forge-workflow★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- forge-buildSkill
- forge-code-reviewSkill
- forge-planSkill
- forge-reviewSkill
- forge-shipSkill
- forge-simplifySkill
- forgeSkill
- forge-verifySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Run this phase only when explicitly invoked through Forge, selected by the caller, or reached by an authorized Forge lifecycle.
- Distinctive: line 35
Follow the owning procedure, loading only applicable support and professionals.
- Distinctive: line 39
Use the shared return contract.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Forge Spec
<skill name="forge-spec">
<activation>
Run this phase only when explicitly invoked through Forge, selected by the caller,
or reached by an authorized Forge lifecycle. Ordinary unselected requests do not
activate portable Forge.
Reuse accepted Launch/authority on resume. Stop at this phase's boundary; an
installed machine name is not evidence of native slash-command support.
</activation>
<setup>
Read [authority](../forge-shared/references/authority.md) and
[target harness resolution](../forge-shared/references/target-harness.md), [Launch and gates](../forge-shared/references/workflows.md),
and the target repository's applicable root/nested harness. Adopt
[Product Manager](../../agents/product-manager/instructions.md) as primary professional guidance.
Product Manager owns product intent. Use Engineer for Bug diagnosis, Designer for triggered experience, Architect for triggered contracts, and Researcher for missing external evidence; sequence dependent authors.
Load the triggered [Designer](../../agents/designer/instructions.md),
[Architect](../../agents/architect/instructions.md),
[Engineer](../../agents/engineer/instructions.md), or
[Researcher](../../agents/researcher/instructions.md) guidance before assignment;
[Reviewer](../../agents/reviewer/instructions.md) owns the separate boundary check.
</setup>
<workflow>
<step n="1" name="Bind the assignment">
Identify the accepted outcome/source revision, selected workflow/depth/control,
requested boundary, actual candidate/state, allowed writes, required proof, and
material unresolved choices. Show or reuse Launch before dispatch or edits.
</step>
<step n="2" name="Perform the phase">
Follow the [owning procedure](references/spec.md), loading only applicable
support and professionals. Read [boundary review](references/boundary-review.md) for the separate fidelity check. Compare the authored Project/Issue against its selected template before handoff.
</step>
<step n="3" name="Inspect and return">
Use the [shared return contract](../forge-shared/references/returns.md). The
accountable owner opens the actual result and relevant new log entries before
advancement, checking the selected template/rubric, candidate, actual evidence,
and gaps. Correct incomplete handoffs; do not promote self-reports into proof.
</step>
</workflow>
<output>
Choose the [Project](assets/product.md), [Issue](assets/issue.md),
[Bug Issue](assets/bug.md), [Design](assets/design.md), [Technical](assets/tech.md),
or [Work](assets/work.md) template under the owning procedure. Preserve the
selected contract; Issue never defaults to the Project format. Keep a ready
small Issue brief. Preserve actual results, findings and remedy authority, evidence limits,
and the direct-phase stopping boundary.
</output>
<checklist>
- Requested phase, authority, Launch, and applicable target harness resolved.
- Owning procedure/template and applicable professional instructions loaded.
- Shared pragmatic severity and scope rules applied to findings and remedies.
- Actual result, required independent return, and relevant new log evidence inspected.
- Unsupported checks remain incomplete; next phase/publication is not implied.
</checklist>
</skill>Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.