メニュー
This skill should be used when the user asks to "create a workspace directory", "workspace-id", "作業ディレクトリを作成", "agent workspace", or wants canonical agent workspace naming and directory conventions.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
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 | workspace-id |
| description | This skill should be used when the user asks to "create a workspace directory", "workspace-id", "作業ディレクトリを作成", "agent workspace", or wants canonical agent workspace naming and directory conventions. |
| tools | ["Bash(${CLAUDE_PLUGIN_ROOT}/skills/workspace-id/generate.ts *)"] |
This skill provides the canonical format and conventions for managing agent workspaces. Use this skill when creating new workspace directories or documenting workspace-related workflows.
Workspace IDs follow a strict format to ensure consistency across all agent work:
yyyymmdd-HHmm-[feature-name]
yyyymmdd
20260302HHmm
1430doc-engine/^[a-z][a-z0-9]*(-[a-z0-9]+)*$/fix-parser, add-auth, refactor-utils, v2-migrationAll workspace files are organized under the .agents/workspaces/ directory:
.agents/workspaces/
└── [workspace-id]/
├── [nnnnnn]-[subagent-name]-[content].md
├── [nnnnnn]-[subagent-name]-[content].md
└── ...
The .agents/workspaces/[workspace-id]/ directory contains all reports and artifacts from a single agent work session.
Files within a workspace use a structured naming pattern:
[nnnnnn]-[subagent-name]-[content].md
[nnnnnn]
000001[subagent-name]
documentation-engineer[content]
reportreport, review, plan)000001-documentation-engineer-report.md — Initial report from documentation engineer000002-code-review-assistant-review.md — Code review from code review assistant000003-api-designer-feedback.md — Feedback from API designerThe generate.ts tool generates a properly formatted workspace ID:
${CLAUDE_PLUGIN_ROOT}/skills/workspace-id/generate.ts [feature-name]
Parameters:
[feature-name] — The kebab-case feature name for your workspaceOutput:
yyyymmdd-HHmm-[feature-name]Example:
${CLAUDE_PLUGIN_ROOT}/skills/workspace-id/generate.ts doc-review
# Output: 20260302-1430-doc-review
Workspace ID: 20260302-1430-doc-engine
Directory: .agents/workspaces/20260302-1430-doc-engine/
Files:
- 000001-documentation-engineer-report.md
- 000002-technical-writer-review.md
- 000003-qa-expert-feedback.md
doc-engine — Documentation system buildingapi-v2-migration — API v2 migration workfix-type-checking — Type checking fixesadd-e2e-tests — Adding end-to-end testsrefactor-auth — Authentication refactoring❌ 20260302-14:30-doc-engine # Time format wrong (use HHmm, not HH:mm)
❌ 20260302-1430-docEngine # Feature name not kebab-case (docEngine)
❌ 20260302-1430-doc_engine # Feature name uses underscore (use hyphens)
❌ 2026-03-02-1430-doc-engine # Date format wrong (use yyyymmdd)
docEngine — Camel-case (must be kebab-case)doc_engine — Underscores (use hyphens only)DOC-ENGINE — Uppercase (must be lowercase)2-doc-engine — Starts with digit (must start with letter)doc--engine — Double hyphens (use single hyphens)❌ 1-doc-engineer-report.md # Only 1 digit (use 6)
❌ 000001-doc engineer-report.md # Space in subagent name
❌ 000001_documentation_engineer_report.md # Underscores (use hyphens)
❌ 000001-documentation-engineer # Missing .md extension
Workspace-ids generated with this skill are automatically persisted. After Auto Compact or when resuming a session, the workspace-id is restored automatically.
The rounds/ directory structure (e.g., rounds/[NNNN]/) is specific to the plan plugin and is NOT part of the general workspace-id specification. Use workspace directories as defined above for standard agent work.
When creating workspaces for plugin-specific work:
.agents/plans/ files and may organize rounds within workspaces.agents/workspaces/[workspace-id]/.agents/workspaces/[workspace-id]/.agents/workspaces/[workspace-id]/All plugins use the same canonical workspace-id format defined by this skill.