菜单
Takes a loose idea and transforms it into a structured, actionable spec ready for implementation. Use when the user passes an idea, feature request, or problem description that needs scoping before building.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Release pipeline for already-done local work. Dispatches /ground-state pre-flight, runs the project test suite, drafts a commit message for user approval, pushes, and opens a PR with a structured verification summary. Use when local changes are ready to hand off to review — e.g. 'ship this', 'push and open a PR', 'release this work'. Add --verify to trigger an adversarial verifier wave on the diff before a human reads the PR.
Surface recurring friction from Claude Code's native telemetry and identify actionable skill opportunities. Use when the user runs /forge-friction.
Bootstraps a dispatchable Claude sub-agent skill for every coding agent CLI installed on this machine (codex, aider, cursor, etc.). Use when the user wants to delegate tasks to locally-installed agent CLIs or expand the plugin's agent fleet.
Map a web UI and generate a Claude automation skill via parallel reconnaissance, synthesis, and iterative validation.
Set up a scheduled headless Claude run that sends summaries to Telegram. Use when the user wants to automate a recurring task via launchd (macOS) with push-notified results.
Reference convention for sub-agent I/O schemas. Loaded by orchestrator skills via /agent-workflow-amplifiers:contract and into agents (e.g., qualify) via the `skills:` field.
| name | spec |
| description | Takes a loose idea and transforms it into a structured, actionable spec ready for implementation. Use when the user passes an idea, feature request, or problem description that needs scoping before building. |
| argument-hint | <idea or feature request> |
Dispatch two sub-agents in parallel. One researches the web for prior art, APIs, and patterns relevant to $ARGUMENT. The other inspects the local codebase for conventions, dependencies, and integration points. When both return, synthesize a concise spec covering: problem, goals, non-goals, approach, key decisions, interface, file plan, test plan, and open questions. Present to the user for confirmation before proceeding.
