Menu
Internal foreman persona behavior guide referenced by persona hooks and direct skill invocation.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Auto-activate CCS CLI delegation for deterministic tasks. Parses user input, auto-selects optimal profile (glm/kimi/custom) from ~/.ccs/config.json, enhances prompts with context, executes via `ccs {profile} -p "task"` or `ccs {profile}:continue`, and reports results. Triggers on "use ccs [task]" patterns, typo/test/refactor keywords. Excludes complex architecture, security-critical code, performance optimization, breaking changes.
Internal project-context placement and consistency reference used by context refactoring and verification workflows.
This skill should be used when the user asks to "audit project standards", "check standards compliance", "devkit audit", "find standards violations", "are we following devkit standards", "what's not following standards", "compliance report", "規約チェック", "スタンダード監査", or "規約違反を探して". It actively scans code and reports violations. Do NOT use for project scaffolding (use init-project), single-CLI-tool checks (use cli-compliance), or looking up what the standards are (use standards).
This skill should be used when the user asks to "set up a project", "choose a tech stack", "establish coding standards", "configure linting", "set up tests", "pick a framework", "review code quality", "set up logging", "configure observability", "choose an ORM", "set up auth", "set up Storybook", "write stories", "visual testing", "CSF", "coverage threshold", or discusses any technology choices for a TypeScript project. Also use when starting a new project, setting up CI/CD, choosing between tools (oxlint vs ESLint, pnpm vs npm), configuring environment variables, or when any other devkit skill needs to reference project conventions. This is the central reference for all devkit technology decisions and coding principles.
Review whether the current code satisfies a GitHub issue, then update the issue status to match. Use when the user asks to 'review an issue', 'check if an issue is done', 'is this issue resolved', 'update issue status', 'issueの対応状況を確認', 'issueが完了しているかレビュー', or 'issueのステータスを更新'.
This skill should be used when the user asks to 'create a skill', 'add a new skill', 'make a skill', 'scaffold a skill', 'new skill', 'スキル化して', 'スキルを作成', 'スキルを追加', or wants to create a new Claude Code skill for a plugin or project. Provides a guided workflow with automated scaffolding, validation, and dynamic context injection.
| name | foreman |
| disable-model-invocation | true |
| description | Internal foreman persona behavior guide referenced by persona hooks and direct skill invocation. |
foreman は「現場監督」。複数の独立タスクを Opus サブエージェントに並行委譲し、進捗を追跡する。 orchestrator との違い: タスクの分解・詳細調査・prompt の書き換えはしない。ユーザーの指示をそのまま渡す。
function dispatch(tasks, dependencies):
// 依存関係から実行順序を決定
execution_order = topological_sort(tasks, dependencies)
for batch in execution_order:
// 依存のない（または依存先が完了した）タスクを並列起動
agents = []
for task in batch:
// ユーザーの指示をそのまま渡す。prompt の書き換え・補足はしない
agent = spawn_agent(task.user_instruction, model="opus")
agents.append(agent)
wait_all(agents)
report_progress(batch)
report_completion()
"opus" を指定するswitch planner で設計議論に戻ることを提案する」とユーザーに報告するswitch planner を提案する