Skip to main content
gsd-tools Central utility skill for GSD operations. Provides config parsing, slug generation, timestamps, path operations, and orchestrates calls to other specialized skills. Acts as the unified entry point that the original gsd-tools.cjs provided via its lib/ modules (commands, config, core, init).
インストールへ移動 Skills Marketplace コミュニティが作成したAIスキルを発見・探索
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/a5c-ai/babysitter --skill gsd-toolsコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Zipをダウンロード ダウンロード中... このリポジトリの他の Skills Reference for querying the Atlas knowledge graph through its MCP tools — the SECONDARY enrichment/comparison layer that adds best-practice context to systems you have ALREADY scanned from your real sources (`az`, repos, dirs). Use when you need to look up nodes, edges, kinds, clusters, stats, or wiki pages in Atlas to compare against your real inventory. (atlas graph, query atlas, atlas mcp, search the graph, graph neighbors, atlas record, atlas kinds, enrichment layer)
Atlas turns your STATED NEED into a real systems atlas by SCANNING your actual sources (Azure via `az`, git repos, local dirs) and process/data mining them, THEN enriching against the Atlas knowledge graph. Use this skill when asked to inventory/map your real systems, scan your cloud + repos + directories, mine the real processes or data they contain, or collect their real constraints/gotchas. (atlas, scan my systems, inventory our azure account, map my repos, real systems atlas, process mining, data mining, collect nuances, system discovery)
assimilate-popular-workflows This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable processes, babysitter plugins, and reusable procedural insights. Searches GitHub for SKILL.md files, classifies repos by archetype, and maintains structured research under docs/reference-repos/.
name gsd-tools description Central utility skill for GSD operations. Provides config parsing, slug generation, timestamps, path operations, and orchestrates calls to other specialized skills. Acts as the unified entry point that the original gsd-tools.cjs provided via its lib/ modules (commands, config, core, init). allowed-tools Bash(*) Read Write Edit Glob Grep metadata {"author":"babysitter-sdk","version":"1.0.0","category":"gsd-core","backlog-id":"SK-GSD-001"} graph {"domains":["domain:software-engineering"],"skillAreas":["skill-area:agentic-loops","skill-area:orchestration-loop"],"workflows":["workflow:feature-development"],"topics":["topic:developer-experience"],"roles":["role:tech-lead","role:backend-engineer"]}
Load and manage .planning/config.json configuration
Generate deterministic slugs from descriptions (kebab-case, deduplication)
Format timestamps for GSD artifact headers and frontmatter
Resolve paths within the .planning/ directory structure
Parse and normalize phase numbers (integer and decimal)
Manage sequential quick task numbering in .planning/quick/
Initialize and validate .planning/ directory structure
Detect project state (new project, existing project, mid-phase, etc.)
Capabilities
1. Configuration Loading Load and parse .planning/config.json with defaults:
{
"profile" : "balanced" ,
"autoCommit" : true ,
"autoVerify" : true ,
"planCheckerEnabled" : true ,
"maxPlanRevisions" : 2 ,
"waveParallelization" : true ,
"contextMonitor" : true ,
"contextWarningThreshold" : 70 ,
"contextCriticalThreshold" : 85 ,
"summaryVariant" : "standard" ,
"tddEnabled" : false ,
"questioningDepth" : "adaptive"
}
cat .planning/config.json
If config does not exist, create with defaults. Merge user overrides with defaults (user values take precedence).
2. Slug Generation Generate kebab-case slugs from descriptions:
Input: "Add user authentication with OAuth2"
Output: "add-user-authentication-with-oauth2"
Input: "Fix bug #123 in payment processing"
Output: "fix-bug-123-in-payment-processing"
Lowercase all characters
Replace spaces and special characters with hyphens
Remove consecutive hyphens
Trim leading/trailing hyphens
Maximum 60 characters (truncate at word boundary)
Check for duplicates in target directory, append -2, -3 if needed
3. Timestamp Formatting Format timestamps for GSD artifacts:
Header: "2026-03-02T14:30:00Z"
Frontmatter: "2026-03-02"
Filename: "20260302-143000"
Display: "Mar 2, 2026 2:30 PM"
4. Path Operations Resolve paths within .planning/ structure:
Phase directory: .planning/phase-{N}/
Plan file: .planning/phase-{N}/PLAN-{M}.md
Summary file: .planning/phase-{N}/SUMMARY.md
Quick task: .planning/quick/{NNN}-{slug}/
Debug session: .planning/debug/{slug}.md
Codebase docs: .planning/codebase/
Research docs: .planning/research/
Milestone archive: milestones/v{X}.{Y}/
5. Phase Number Parsing Parse integer and decimal phase numbers:
"72" -> { major: 72, minor: null, display: "72" }
"72.1" -> { major: 72, minor: 1, display: "72.1" }
"72.2" -> { major: 72, minor: 2, display: "72.2" }
Decimal phases are inserted phases (e.g., urgent work between phase 72 and 73).
6. Quick Task Numbering Sequential numbering for quick tasks:
.planning/quick/001-fix-login-bug/
.planning/quick/002-add-rate-limiting/
.planning/quick/003-update-readme/
Scan existing directories, find highest number, increment by 1. Zero-pad to 3 digits.
7. Planning Directory Initialization Ensure .planning/ directory exists with required structure:
.planning/
config.json
PROJECT.md (if new-project has run)
REQUIREMENTS.md (if new-project has run)
ROADMAP.md (if new-project has run)
STATE.md (always present after init)
quick/ (created on demand)
debug/ (created on demand)
codebase/ (created on demand)
research/ (created on demand)
8. Project State Detection Detect current project state for routing:
const states = {
NO_PROJECT : "No .planning/ directory or no PROJECT.md" ,
INITIALIZED : ".planning/ exists with PROJECT.md but no phases started" ,
MID_PHASE : "A phase is in progress (has plans but no summary)" ,
PHASE_COMPLETE : "Current phase complete, ready for next" ,
MILESTONE_READY : "All milestone phases complete, ready for audit" ,
BLOCKED : "STATE.md has active blockers"
};
Tool Use Instructions
Reading Configuration
Use Read to load .planning/config.json
Parse JSON and merge with defaults
Return merged configuration object
Generating Slugs
Accept description string as input
Apply slug transformation rules
Use Glob to check for duplicates in target directory
Append deduplication suffix if needed
Return final slug
Initializing Planning Directory
Use Bash to create directory structure with mkdir -p
Use Write to create config.json with defaults if missing
Use Read + Glob to detect existing state
Return initialization status
Process Integration This skill is used by all GSD processes as the first initialization step:
new-project.js - Initialize .planning/, create configplan-phase.js - Resolve phase paths, load config for planner settingsexecute-phase.js - Load config for executor settings, resolve task pathsquick.js - Generate quick task number and slug, resolve quick task pathdebug.js - Generate debug session slug, resolve debug pathprogress.js - Detect project state, load configcomplete-milestone.js - Resolve milestone archive pathadd-tests.js - Resolve phase paths for test generationresearch-phase.js - Resolve research output paths
Output Format {
"operation" : "init|config|slug|path|state" ,
"status" : "success|error" ,
"result" : {
"config" : { } ,
"slug" : "generated-slug" ,
"path" : "/resolved/path" ,
"state" : "NO_PROJECT|INITIALIZED|MID_PHASE|..."
} ,
"metadata" : {
"planningDir" : ".planning/" ,
"configPath" : ".planning/config.json" ,
"timestamp" : "2026-03-02T14:30:00Z"
}
}
Configuration Setting Default Description profilebalancedModel profile (quality/balanced/budget) autoCommittrueAuto-commit after each task autoVerifytrueAuto-verify after phase execution planCheckerEnabledtrueRun plan checker before execution maxPlanRevisions2Max plan revision cycles waveParallelizationtrueEnable wave-based parallel execution contextMonitortrueEnable context window monitoring summaryVariantstandardSummary template variant
Error Handling Error Cause Resolution Config parse errorMalformed config.json Reset to defaults, warn user Planning dir not writablePermission issue Check filesystem permissions Slug collision limit10+ duplicates with same slug Use timestamp suffix instead Phase number invalidNon-numeric phase argument Show valid format examples State detection failureCorrupt STATE.md Suggest health command to repair
Constraints
Never modify files outside .planning/ directory without explicit instruction
Config defaults must be backward-compatible with existing projects
Slug generation must be deterministic (same input = same output, ignoring dedup)
Phase number parsing must handle both integer and decimal formats
Quick task numbering must be sequential with no gaps
All path operations must use forward slashes for cross-platform compatibility
