forge-plan
Skill13 starsChanged 44 days agoMITView on GitHub
Translate accepted intent into a proportionate implementation strategy. Use for "Forge plan", asking Forge to plan an Issue, or a caller-selected Plan phase. Stops before implementation; does not create requirements or authorize Build.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- KhaledAufDB/lakeforgetheir own version, first seen Oct 13, 2026
- Dshamir/slm-forgetheir own version, first seen Oct 13, 2026
- tinyorbit-ai/skillstheir own version, first seen Aug 20, 2026
- khaledayeva/star-forgetheir own version, first seen Jul 26, 2026
- redteamlife/forgetheir own version, first seen Jul 26, 2026
- orkait/hyperstacktheir own version, first seen Jun 14, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- tonmoy007/forge-plugins★ 2same name
- Dshamir/slm-forge★ 1same name
- khaledayeva/star-forge★ 1same name
- orkait/hyperstack★ 1same name
- redteamlife/forge★ 1same name
- tinyorbit-ai/skills★ 1same name
- KhaledAufDB/lakeforge★ 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-reviewSkill
- forge-shipSkill
- forge-simplifySkill
- forgeSkill
- forge-specSkill
- forge-verifySkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
3
Distinctive
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 31
Follow the owning procedure, loading only applicable support and professionals.
- Distinctive: line 35
Use the shared return contract.
- Distinctive: line 42
Use the existing plan artifact template when a separate artifact is earned.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Forge Plan
<skill name="forge-plan">
<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
[Engineer](../../agents/engineer/instructions.md) as primary professional guidance.
Engineer owns technical strategy and proof. [Product Manager](../../agents/product-manager/instructions.md) authors only missing
product scope and outcome criteria.
</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/plan.md), loading only applicable
support and professionals. A brief Quick Plan may stay in an existing Issue or Build log. Consequential choices follow the shared gates; reversible tactics remain with the Builder.
</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>
Use [the existing plan artifact template](assets/plan.md) when a separate
artifact is earned; otherwise record its applicable information in the existing
Issue/log. 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.