Agent skills for structured development with pluggable issue tracking.
One workflow. Six skills. From idea to review-ready code.
Context · Architecture · Development · Guidelines · Testing · PR Workflow
A forge is where raw material meets intention. You bring the codebase — these skills shape the workflow from issue to implementation to review.
Forge skills follow the Agent Skills open standard and work with any compatible agent.
| Skill | Command | Purpose |
|---|---|---|
| Setup Project | /forge-setup-project |
Set up or audit a project's context infrastructure for agentic engineering |
| Shape | /forge-shape |
Shape a vague idea into a clear plan through one-at-a-time structured questioning |
| Create Issue | /forge-create-issue |
Collaboratively plan and create Issues (GitHub, markdown, or other provider) |
| Implement | /forge-implement <input> |
Implement from an Issue, plan file, or description |
| Reflect | /forge-reflect |
Self-review changes (PR, branch, or uncommitted) |
| Address PR Feedback | /forge-address-pr-feedback |
Address unresolved PR review comments |
| Ship | /forge-ship <input> |
Implement + review in one invocation |
Skills with structured primary input also accept optional trailing execution guidance using -- <additional context>.
The skills form a simple workflow — each step feeds into the next:
forge-setup-project → [forge-shape →] forge-create-issue → forge-implement → forge-reflect → forge-address-pr-feedback
╰──── forge-ship ────╯
forge-ship composes implement + review into a single invocation. Review stays lean by default — tiny low-risk diffs stay inline; otherwise use one fresh-context reviewer, with a second pass only when risk justifies it. Scout and review work should use cheaper models when the runtime supports per-task model choice; otherwise they should inherit the parent session model cleanly.
Forge skills follow the Agent Skills open standard and work with any compatible agent.
Via npx skills — auto-detects your agents and installs to all of them:
npx skills add mgratzer/forgeManual — symlink into your agent's skills directory:
ln -s /path/to/forge/skills/forge-* /path/to/forge/skills/_shared <your-agent-skills-dir>/Both forge-* skills and the _shared/ directory are required — skills reference shared modules via ../_shared/ paths. Check your agent's docs for the correct skills directory path.
AGENTS.mdis the canonical project guidance fileCLAUDE.mdis a compatibility symlink for tools that still look for that filename
| Document | Purpose |
|---|---|
| Context | Shared vocabulary used across forge skills |
| Architecture | Skill workflow, file format, design decisions |
| Development | How to create and modify skills |
| Coding Guidelines | Skill authoring conventions and style rules |
| Testing | How to validate skills manually |
| PR Workflow | Commits, PRs, branch naming, review process |
- Read AGENTS.md for project principles and conventions
- Follow docs/coding-guidelines.md for skill authoring rules
- Test your changes by invoking the skill on a real project
- Use conventional commits:
feat(skills): add new skill