How do I install the Work On skill?

Run npx skillmds@latest add rapiercraftstudios/work-on in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Work On safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Work On?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Work On free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Work On?

rapiercraftstudios (@rapiercraftstudios) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Work On by rapiercraftstudios — Agent Skill

Name: Work On
Author: rapiercraftstudios

File contents

Forge Repo Adapter: work-on

Use commands/work-on.md as the authoritative state-machine source, but apply the Forge repo overrides below when running from Codex in this repository.

Repo Resolution Override

Inside the Forge repo, resolve issue targets like this unless the user explicitly prefixes another project:

Input	Repo
`123`, `#123`, `next`, empty	`RapierCraftStudios/forgedock`
`forge:123`	`RapierCraftStudios/forgedock`

Satellite prefixes (e.g. mcp:5, sdk:12) are project-specific and defined in forge.yaml → repos.satellites. See commands/work-on.md Phase 0B for multi-repo routing.

For Forge repo issues, set:

GH_REPO=RapierCraftStudios/forgedock
GH_FLAG=--repo RapierCraftStudios/forgedock
REPO_PATH=/home/mrdubey/projects/forgedock
STAGING_BRANCH=staging
DEFAULT_BRANCH=main

Codex Runtime Overrides

Treat any .claude/worktrees/... example path in the shared command spec as .codex/worktrees/... for Codex execution in this repo.
Create and reuse worktrees under /home/mrdubey/projects/forgedock/.codex/worktrees.
Prefer gh api repos/{GH_REPO}/issues/{NUMBER}/comments for comment reads instead of gh issue view --comments.
Treat GitHub Project-board sync as best-effort only for Forge issues. Do not block the pipeline if Forge-specific board/component mappings are absent.
Create missing workflow:* labels on demand if the Forge repo does not already have them.

Forge Repo File Scope

When the shared workflow says to inspect domain files, prioritize Forge repo files instead:

commands/**/*.md
docs/**/*.md
scripts/**/*.sh
install.sh, install-codex.sh, update.sh
AGENTS.md, CLAUDE.md, CHANGELOG.md
.agents/skills/**/*.md

Subcommand Mapping

When commands/work-on.md invokes nested skills, use these Codex adapters:

work-on:investigate -> repo-local .agents/skills/work-on/investigate/SKILL.md
work-on:build -> repo-local .agents/skills/work-on/build/SKILL.md
work-on:review -> repo-local .agents/skills/work-on/review/SKILL.md
work-on:close -> installed forge-work-on-close
work-on:decompose -> installed forge-work-on-decompose

If an installed forge-* skill exists for the nested command, use it. Otherwise read the referenced shared command file directly and continue manually.

Execution Rule

Preserve the shared Forge behavior from commands/work-on.md: GitHub state is the memory layer, FORGE:* comments remain machine-readable, and the routing loop continues until an explicit terminal condition is reached.

---name: work-ondescription: Pick up a GitHub issue and run the full investigate-build-review-merge pipeline for Forge from Codex.---# Forge Repo Adapter: work-onUse `commands/work-on.md` as the authoritative state-machine source, but apply the Forge repo overrides below when running from Codex in this repository.## Repo Resolution OverrideInside the Forge repo, resolve issue targets like this unless the user explicitly prefixes another project:| Input | Repo ||---|---|| `123`, `#123`, `next`, empty | `RapierCraftStudios/forgedock` || `forge:123` | `RapierCraftStudios/forgedock` |Satellite prefixes (e.g. `mcp:5`, `sdk:12`) are project-specific and defined in `forge.yaml → repos.satellites`. See `commands/work-on.md` Phase 0B for multi-repo routing.For Forge repo issues, set:- `GH_REPO=RapierCraftStudios/forgedock`- `GH_FLAG=--repo RapierCraftStudios/forgedock`- `REPO_PATH=/home/mrdubey/projects/forgedock`- `STAGING_BRANCH=staging`- `DEFAULT_BRANCH=main`## Codex Runtime Overrides- Treat any `.claude/worktrees/...` example path in the shared command spec as `.codex/worktrees/...` for Codex execution in this repo.- Create and reuse worktrees under `/home/mrdubey/projects/forgedock/.codex/worktrees`.- Prefer `gh api repos/{GH_REPO}/issues/{NUMBER}/comments` for comment reads instead of `gh issue view --comments`.- Treat GitHub Project-board sync as best-effort only for Forge issues. Do not block the pipeline if Forge-specific board/component mappings are absent.- Create missing `workflow:*` labels on demand if the Forge repo does not already have them.## Forge Repo File ScopeWhen the shared workflow says to inspect domain files, prioritize Forge repo files instead:- `commands/**/*.md`- `docs/**/*.md`- `scripts/**/*.sh`- `install.sh`, `install-codex.sh`, `update.sh`- `AGENTS.md`, `CLAUDE.md`, `CHANGELOG.md`- `.agents/skills/**/*.md`## Subcommand MappingWhen `commands/work-on.md` invokes nested skills, use these Codex adapters:- `work-on:investigate` -> repo-local `.agents/skills/work-on/investigate/SKILL.md`- `work-on:build` -> repo-local `.agents/skills/work-on/build/SKILL.md`- `work-on:review` -> repo-local `.agents/skills/work-on/review/SKILL.md`- `work-on:close` -> installed `forge-work-on-close`- `work-on:decompose` -> installed `forge-work-on-decompose`If an installed `forge-*` skill exists for the nested command, use it. Otherwise read the referenced shared command file directly and continue manually.## Execution RulePreserve the shared Forge behavior from `commands/work-on.md`: GitHub state is the memory layer, `FORGE:*` comments remain machine-readable, and the routing loop continues until an explicit terminal condition is reached.

Frequently asked questions

Work On