forge-plan SKILL.md skillA
forge-plan from brightstack/forge is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add brightstack/forge/forge-plan@git:20261019.7e38045Pins git:20261019.7e38045 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- brightstack/forge
- Path
skills/forge-plan/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261019.7e38045, committed Oct 19, 2026
- Size
- 2,910 bytes
- Repository stars
- 12
- License
- MIT
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 …
Read the whole file at its exact version.
How to install
mdr add brightstack/forge/forge-plan@sha256:d1e707d01b4f91fbThe line at the top of this page pins the label git:20261019.7e38045, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_rov7wbyut3wsrhqn)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 19, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2910 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
brightstack/forge · 12 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rov7wbyut3wsrhqn GET https://markdownregistry.com/api/v1/resolve?ref=brightstack/forge/forge-plan GET https://markdownregistry.com/api/v1/blob/d1e707d01b4f91fbe63ac96ebea8da4fc9e0c921fdd65cc2c981065844f55f2b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.