Planning workflow patterns: SOW generation, Spec creation, Q&A clarification, validation. Provides templates and processes for structured planning before implementation. Triggers: SOW, Spec, planning, validation, acceptance criteria, requirements, /think, /sow, /spec.
Provides templates and processes for structured planning workflows including SOW generation, spec creation, and validation.
/plugin marketplace add thkt/claude-config/plugin install complete-workflow-system@thkt-development-workflowsThis skill is limited to using the following tools:
references/sow-generation.mdreferences/spec-generation.mdreferences/think-workflow.mdreferences/validation-criteria.mdPlanning workflow patterns for SOW, Spec, and validation processes.
Centralize planning workflow patterns that were embedded in individual commands. Commands become thin orchestrators that reference this skill for planning logic.
| Workflow | Reference | Command |
|---|---|---|
| SOW Generation | @./references/sow-generation.md | /sow |
| Spec Generation | @./references/spec-generation.md | /spec |
| Think Orchestration | @./references/think-workflow.md | /think |
| Validation | @./references/validation-criteria.md | /validate |
/research → /think → /code → /test → /audit → /validate
│ │
│ ├── Q&A clarification
│ ├── SOW generation
│ └── Spec generation
│
└── Investigation only (no implementation)
| Section | Purpose |
|---|---|
| Executive Summary | 1-2 sentence overview |
| Problem Analysis | Current state, issues |
| Assumptions | Facts, assumptions, unknowns |
| Solution Design | Approach, alternatives |
| Acceptance Criteria | AC-001, AC-002, ... |
| Implementation Plan | Phases, progress matrix |
| Risks | R-001, R-002, ... |
| Section | Purpose |
|---|---|
| Functional Requirements | FR-001, FR-002, ... |
| Data Model | TypeScript interfaces |
| Implementation | Phase mapping, commands |
| Test Scenarios | T-001, T-002, ... |
| Non-Functional Requirements | NFR-001, NFR-002, ... |
| Traceability Matrix | AC → FR → Test → NFR |
| Marker | Confidence | Usage |
|---|---|---|
| [✓] | >0.8 | Verified (file:line required) |
| [→] | 0.5-0.8 | Inferred (state reasoning) |
| [?] | <0.5 | Hypothesis (needs confirmation) |
~/.claude/templates/sow/workflow-improvement.md
~/.claude/templates/spec/workflow-improvement.md
~/.claude/templates/summary/review-summary.md
orchestrating-workflows - Implementation workflows/think - Full planning orchestration/sow - SOW generation/spec - Spec generation/validate - SOW validation/plans - List planning documentsThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.