Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
/plugin marketplace add udecode/dotai/plugin install plan@dotaiThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
🚨 CRITICAL REQUIREMENT: Create the plan file .claude/docs/plans/<topic>-design.md BEFORE asking questions, then update it incrementally after EACH answer. Do NOT wait until the end to write everything at once.
Start by understanding the current project context, then ask multiple related questions together (up to 4 at once) to efficiently refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.
CRITICAL FIRST STEP - Create Plan File Immediately:
.claude/docs/plans/<topic>-design.md using Write toolUnderstanding the idea:
Exploring approaches:
Presenting the design:
THIS SKILL IS FOR DESIGN ONLY. If you find yourself writing implementation details, STOP - you're crossing into writing-plans territory.
DESIGN (this skill) - High-level, conceptual:
IMPLEMENTATION (writing-plans skill) - Detailed, executable:
Red Flags - STOP Immediately:
If you catch yourself doing any of the above, immediately:
Documentation:
.claude/docs/plans/<topic>-design.md should already exist and be completeIncremental Writing Pattern (THE CORRECT WAY):
WRONG ❌:
1. Ask all questions
2. Get all answers
3. Write entire plan at the end
CORRECT ✅:
1. Write initial plan file with problem statement
2. Ask question batch 1
3. Immediately update plan file with answers
4. Ask question batch 2
5. Immediately update plan file with answers
6. Present design section by section
7. Update plan file with any refinements
8. Final review and polish
Example workflow:
.claude/docs/plans/2025-11-05-pcc-sync-design.md with initial understandingThe plan file is your working document, not a final deliverable to write at the end
Implementation (if continuing):
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 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 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.