6,336 件 ・ 関連度順
概要と使いどころ
Design agent system prompts with explicit behavior rules and cognitive control. This skill should be used when users need to define agent instructions, create intent-to-tool mappings, establish confirmation policies, or prevent hallucinated actions in AI agents.
日本語の概要は準備中です。原文の説明を表示しています。
Standardized output formats for research, planning, implementation, and review agents. Use when generating agent outputs or parsing agent responses.
日本語の概要は準備中です。原文の説明を表示しています。
Agent assistance skill that provides stuck detection, memory management, and session learning capabilities for AI agents Trigger terms: agent stuck, loop detected, session memory, agent learning, condense memory, stuck detection, agent memory, session learnings, extraction Use when: User reports agent is stuck, looping, or needs memory/learning management
日本語の概要は準備中です。原文の説明を表示しています。
Manage persistent memory for autonomous coding. Use when storing/retrieving knowledge, managing Graphiti integration, persisting learnings, or accessing episodic memory.
日本語の概要は準備中です。原文の説明を表示しています。
Build custom AI agents in Claude Code from a user's problem statement. This skill analyzes the user's use case, asks smart clarifying questions, researches the internet for similar agents (GitHub repos, blogs, Claude Code community patterns), and then architects and builds production-ready Claude Code agents — including subagents, skills, hooks, slash commands, MCP integrations, and CLAUDE.md configuration. Use this skill whenever the user wants to create an agent, build an automation workflow, set up a Claude Code subagent, design a multi-agent system, or says things like 'build me an agent for...', 'automate this with Claude Code', 'I want a subagent that...', 'help me create a workflow', 'set up an agent pipeline', or any variation of wanting Claude Code to do something specialized. Also trigger when the user mentions agent architecture, agent SDK, agentic workflows, or task delegation in Claude Code — even if they don't use the word 'agent' explicitly.
日本語の概要は準備中です。原文の説明を表示しています。
Guide Maestro's Linear issue/task journeys using exact team and issue identities, source-scoped controls, state mappings, and repository PR linkage.
日本語の概要は準備中です。原文の説明を表示しています。
High-level reality check when the swarm feels busy but directionally off. Use when lots of code is landing but the real goal still feels far away.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold a new model provider for Forge — class, registry wiring, providerEnum entry, local-catalog classification, router check, and a unit test with mocked transport.
日本語の概要は準備中です。原文の説明を表示しています。
Start a new Flywheel planning round. Produce initial markdown plan, route to competing frontier models, synthesize hybrid, refine 4–5×. Use before any coding begins on a new feature.
日本語の概要は準備中です。原文の説明を表示しています。
Polishing pass over all open beads. "Check your beads N times, implement once." Run 4–6 times. Use after /plan-to-beads and between refinement rounds.
日本語の概要は準備中です。原文の説明を表示しています。
Break the spell of local productivity. Ask whether completing all open beads actually closes the gap to the project goal. Use at milestones or when busy agents feel directionally off.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold a new Forge subagent (planner/architect/executor/reviewer/debugger/memory-style).
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold a new Forge tool end-to-end — implementation, registration, permission/risk metadata, sandbox routing, and a unit test.
日本語の概要は準備中です。原文の説明を表示しています。
Merge duplicate or excessively overlapping beads in .beads/beads.jsonl into canonical ones. Run after any batch where 20+ new beads were created.
日本語の概要は準備中です。原文の説明を表示しています。
Overview of Forge's Agentic Coding Flywheel methodology — plan space, bead space, code space. Invoke this skill when you need to know which Flywheel skill or prompt applies to the current phase.
日本語の概要は準備中です。原文の説明を表示しています。
Remove telltale AI-writing patterns from README, docs, and user-facing text. Must be done line-by-line, manually. No regex. Use after agents write any user-visible prose.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-release checklist for Forge — verify, version bump, changelog, docs, docker build, smoke test. Run before tagging v*.
日本語の概要は準備中です。原文の説明を表示しています。
Reset review context when bead polishing or code review has flatlined. Requires starting a brand-new Claude / Codex session. Use when you're seeing the same small edits round after round.
日本語の概要は準備中です。原文の説明を表示しています。
Deep code review after beads have landed — random exploration + cross-agent review, alternating. Use every 30–60 min during active implementation, or after any epic lands.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold a new Forge tool end-to-end — type, implementation, registration, permission/risk classification, and unit test. Use when adding anything to src/tools/.
日本語の概要は準備中です。原文の説明を表示しています。
Remove AI-writing tells from README, docs, and user-facing text. Must be done line-by-line, no regex. Use after agents write any user-visible prose.
日本語の概要は準備中です。原文の説明を表示しています。
Start a new Flywheel planning round for a Forge feature. Writes the initial markdown plan to .flywheel/plans/ and gives instructions for sending it to competing frontier models. Use at the very beginning of a new feature or subsystem.
日本語の概要は準備中です。原文の説明を表示しています。
Run Forge's canonical verification chain (format:check + lint + typecheck + build + test). Use before claiming any task complete or opening a PR.
日本語の概要は準備中です。原文の説明を表示しています。
Translate a polished markdown plan into self-contained beads in .beads/beads.jsonl. Treat this as a distinct translation problem, not task extraction. Use after /plan-synthesize produces a stable hybrid plan.
日本語の概要は準備中です。原文の説明を表示しています。