quantumbitcz/forge-shape
skills/forge-shape/SKILL.md
[writes] Turn a vague idea into a structured spec with stories and acceptance criteria. Use when your requirement is unclear, you're not sure what to build, or you need to think through a feature before implementing. Trigger: /forge-shape, I have an idea, help me think through this, refine my requirements
development
Updated Apr 20, 2026
$ install --global
skillsauthnpx skillsauth add quantumbitcz/dev-pipeline forge-shapeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 20, 2026, 5:17 AM4.5s1 file scanned
SKILL.md
- name:
- forge-shape
- description:
- [writes] Turn a vague idea into a structured spec with stories and acceptance criteria. Use when your requirement is unclear, you're not sure what to build, or you need to think through a feature before implementing. Trigger: /forge-shape, I have an idea, help me think through this, refine my requirements
- allowed-tools:
- ['Read', 'Write', 'Edit', 'Bash', 'Glob', 'Grep', 'Agent', 'AskUserQuestion']
- ui:
- { ask: true, plan: true }
/forge-shape -- Feature Shaping Entry Point
Flags
- --help: print usage and exit 0
- --dry-run: preview actions without writing
Exit codes
See shared/skill-contract.md for the standard exit-code table.
Prerequisites
Before any action, verify:
- Git repository: Run
git rev-parse --show-toplevel 2>/dev/null. If fails: report "Not a git repository. Navigate to a project directory." and STOP. - Forge initialized: Check
.claude/forge.local.mdexists. If not: report "Forge not initialized. Run /forge-init first." and STOP.
What to Expect
After dispatch, fg-010-shaper will:
- Ask clarifying questions about your requirement (~3-5 questions)
- Propose epics, stories, and acceptance criteria
- Iterate based on your feedback until you're satisfied
- Save the structured spec to
.forge/specs/for use with/forge-run --spec
This is interactive — expect a ~5 minute conversation. The result is a spec file, not code.
Instructions
-
Parse input: The user's argument (everything after
/forge-shape) is the feature idea -- a free-text description like "Add notification system" or "I want users to share plans". If no input is provided, ask the user: "What feature would you like to shape? Describe your idea, even if it's rough (e.g., 'users should be able to share plans with each other')." -
Validate input: Ensure the input contains enough substance to start shaping. A single word is insufficient. If the input is too terse (fewer than 3 words), prompt: "Could you elaborate a bit? What problem does this feature solve, or who is it for?"
-
Detect available MCPs: Detect available MCPs per
shared/mcp-detection.mddetection table. Mark unavailable MCPs as degraded. Build a comma-separated list of detected integrations. -
Dispatch the shaper: Use the Agent tool to invoke
fg-010-shaperwith the following prompt:Shape this feature requirement:
{user_input}Available MCPs:
{detected_mcps}Where
{user_input}is the raw text the user provided. -
Do nothing else: Do not plan, implement, or make decisions. The shaper handles all interaction with the user -- it will ask clarifying questions, propose structure, and iterate until the spec is solid.
-
Relay the result: When the shaper completes, relay its output (spec location, next steps) back to the user unchanged. The output typically includes a path to the generated spec file and a suggestion to run
/forge-run --spec <path>.
Error Handling
| Condition | Action | |-----------|--------| | Prerequisites fail | Report specific error message and STOP | | Empty input | Ask user for feature description before dispatching | | Shaper agent dispatch fails | Report "Feature shaper failed to start. Check plugin installation and try again." and STOP | | Shaper returns error | Relay the error unchanged | | User abandons shaping mid-session | The shaper handles graceful exit. No cleanup needed |
See Also
/forge-run-- Run the full pipeline after shaping is complete (use--spec <path>to pass the shaped spec)/forge-sprint-- Execute multiple shaped features in parallel/forge-fix-- For bug reports rather than new features/forge-bootstrap-- For scaffolding a new project rather than shaping a feature
Related Skills
quantumbitcz/forge
development
VerifiedTrustedCommunity
[writes] Build, fix, deploy, review, or modify code in this project. Universal entry for the forge pipeline. Auto-bootstraps on first run; brainstorms before planning when given a feature description. Use when you want to take any productive action: implementing features, fixing bugs, reviewing branches, deploying, committing, running migrations.
SKILL.mdUpdated Apr 30, 2026
quantumbitcz/forge-admin
tools
VerifiedTrustedCommunity
[writes] Manage forge state and configuration: recovery, abort, config edits, session handoff, automations, playbooks, output compression, knowledge graph maintenance. Use when you need to recover from broken pipeline state, edit settings, or manage long-lived state.
SKILL.mdUpdated Apr 30, 2026
quantumbitcz/forge-handoff
development
VerifiedTrustedCommunity
[writes] Create, list, show, resume, or search forge session handoffs. Use when context is getting heavy and you want to transfer a forge run or conversation into a fresh Claude Code session, or to resume from a prior handoff artefact. Subcommands - no args (write), list, show, resume, search.
SKILL.mdUpdated Apr 23, 2026
quantumbitcz/forge-graph
development
VerifiedTrustedCommunity
[writes] Manage the Neo4j knowledge graph. Subcommands: init, rebuild (writes); status, query <cypher>, debug (read-only). Requires Docker. No default — an explicit subcommand is required. Use when setting up the graph for the first time, rebuilding after major refactors, checking graph health, or running ad-hoc Cypher diagnostics.
SKILL.mdUpdated Apr 21, 2026