Agent skill
configure-forge
Generate workspace-level forge binding prompts and agents from workspace.config.yaml topology
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/configure-forge-daemn256-workspace-repo-templ
SKILL.md
Configure Forge
Uses Workspace Configurator to read the workspace's forge topology and tooling preferences, then generate workspace-level prompts and agents that provide concrete forge operations.
Prerequisites: workspace.config.yaml exists with forge topology and board configuration
Phase 1: Read Configuration
Extract Forge Topology
- Read
workspace.config.yaml - Extract the following settings:
forge.topology— which providers handle repos, boards, CI, releasesforge.tooling.preferred— preferred tool surface (mcp, cli, api)forge.tooling.<provider>— provider-specific tool settingsboard.*— board field IDs and option IDsadapters.ai-runtimes— which runtimes need generated artifacts
- Present extracted configuration for confirmation
Output
## Context Anchors
- **Workspace:** <name>
- **Phase:** 1 — Read Configuration
## Forge Topology
| Setting | Value |
| ------------------------- | ------- |
| `forge.topology.repos` | <value> |
| `forge.topology.boards` | <value> |
| `forge.topology.ci` | <value> |
| `forge.topology.releases` | <value> |
| `forge.tooling.preferred` | <value> |
## Board Configuration
| Field | ID |
| -------------- | ------- |
| project_id | <value> |
| status field | <value> |
| priority field | <value> |
## Next Step
Confirm topology and preferences before generating artifacts.
**Approval Required:** Yes
⛔ CHECKPOINT
STOP. Do not proceed until human explicitly approves:
- Topology settings are correct
- Tooling preferences are appropriate
- Board configuration is complete
Phase 2: Determine Artifacts
Artifact Matrix
Based on topology and tooling preferences, determine what to generate:
| Topology Setting | Tool Preference | Generates |
|---|---|---|
boards: github |
mcp |
Artifacts using GitHub MCP server for issue/board operations |
boards: github |
cli |
Artifacts using gh CLI for issue/board operations |
boards: ado |
cli |
Artifacts using az boards CLI for work item operations |
repos: github |
mcp |
Artifacts using GitHub MCP for repo operations |
repos: github |
cli |
Artifacts using gh CLI for repo operations |
Per-Runtime Output
| Runtime | Output Location | Agent Location |
|---|---|---|
| GitHub Copilot | .github/prompts/forge-ops.prompt.md |
.github/agents/forge-ops.agent.md |
| Claude Code | .claude/skills/forge-ops/SKILL.md |
.claude/agents/forge-ops.md |
Phase 3: Generate
Create Forge Artifacts
- Generate forge operation prompts for each declared concern (issues, PRs, board)
- Generate a forge-ops agent that knows the workspace's specific tooling
- Include board field IDs and option IDs in generated artifacts
- Include error handling for authentication and connectivity
Generated Prompt Structure
# Forge: <Operation Name>
> <What this prompt does>
## Configuration
- **Provider:** <from workspace.config.yaml>
- **Tool surface:** <mcp | cli>
- **Board project:** <project_id>
## Operations
### Create Issue
<Provider-specific commands/tool calls for creating an issue>
### Update Board Status
<Provider-specific commands for setting board field values>
### Create PR
<Provider-specific commands for creating a pull request>
Output
## Context Anchors
- **Workspace:** <name>
- **Phase:** 3 — Generate
- **Forge topology:** <repos>/<boards>/<ci>/<releases>
## Proposed Artifacts
| File | Purpose |
| ------ | ------------- |
| <path> | <description> |
## Next Step
Review generated artifacts before writing.
**Approval Required:** Yes
⛔ CHECKPOINT
STOP. Do not write files until human explicitly approves:
- Generated artifacts are correct
- Tooling preferences are correctly reflected
- Board field IDs are properly included
Phase 4: Write and Verify
Write Generated Artifacts
- Write generated files to appropriate locations
- List what was generated
- Suggest testing the generated prompts
Output
## Context Anchors
- **Workspace:** <name>
- **Forge topology:** <repos>/<boards>/<ci>/<releases>
- **Tooling preference:** <mcp | cli>
## Generated Artifacts
| File | Purpose |
| ------ | ------------- |
| <path> | <description> |
## Next Step
Test the generated prompts by running a forge operation.
**Approval Required:** No
Error Handling
| Error | Recovery |
|---|---|
| workspace.config.yaml missing | Run /setup-workspace first |
| forge.tooling section missing | Use defaults (mcp if available, else cli) |
| Board field IDs missing | Ask human to fill in board configuration |
| Unsupported forge provider | Report limitation, suggest manual configuration |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?