Assist in generating comprehensive plans from templates using extended thinking. Use when generating plans from meta-prompt templates, reviewing plan quality, or ensuring plans meet team standards.
Generates comprehensive implementation plans from templates by analyzing requests, exploring codebase context, and filling sections with specific, actionable details. Claude uses this when creating plans from `/chore`, `/bug`, or `/feature` templates to ensure plans meet team standards for specificity, completeness, and testability.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install google-ecosystem@melodic-softwareThis skill is limited to using the following tools:
Guide for generating high-quality plans from meta-prompt templates.
/chore, /bug, /feature templatesParse the high-level description:
Input: "Add user authentication with OAuth"
Extract:
- Domain: Authentication
- Scope: User-facing, OAuth protocol
- Complexity: Medium-high (external integration)
Use extended thinking for complex planning:
THINK HARD about:
- What files need to change?
- What are the dependencies?
- What could go wrong?
- How will we verify success?
Gather context before planning:
Complete every section with specifics:
## Relevant Files
- src/auth/OAuthProvider.ts (create)
- src/auth/index.ts (modify - add export)
- src/config/oauth.ts (create)
- tests/auth/oauth.test.ts (create)
Check against quality criteria before finalizing.
Every plan should meet these standards:
Bad: "Update the component" Good: "Update UserProfile.tsx to add loading state on line 45"
Bad: "Handle errors appropriately" Good: "Add try/catch in fetchUser(), log errors with console.error, show ErrorBoundary"
All template sections filled:
Every plan must include validation:
## Validation Commands
- Run `npm test -- auth` to verify unit tests pass
- Run `npm run e2e -- oauth` to verify integration
- Manual: Complete OAuth flow in browser
Focus on:
Focus on:
Focus on:
Problem: "Implement the feature" Fix: Break into specific sub-tasks with file references
## Step by Step Tasks
1. Create AuthContext in src/contexts/AuthContext.tsx
2. Add useAuth hook in src/hooks/useAuth.ts
3. Wrap App component with AuthProvider in src/App.tsx
4. Add login route in src/routes/index.tsx
Problem: Plan doesn't mention test files Fix: Always include test file creation/modification
## Relevant Files
- src/components/Login.tsx (create)
- src/components/Login.test.tsx (create) # Tests!
Problem: "Make sure it works" Fix: Specific commands with expected outcomes
## Validation Commands
- Run `npm test` - expect 0 failures
- Run `npm run build` - expect successful build
- Run `npm run lint` - expect 0 errors
Problem: Plan addresses more than requested Fix: Stay focused on original request, note related work in Notes
## Notes
- Related: Login form could use accessibility improvements (separate chore)
- Related: Password reset flow needs similar OAuth option (separate feature)
Use these phrases to activate deeper reasoning:
| Phrase | When to Use |
|---|---|
| "think" | Simple plans, clear path |
| "think hard" | Medium complexity, some unknowns |
| "think harder" | Complex integration, many dependencies |
| "ultrathink" | Architecture decisions, high-risk changes |
specs/[type]-[descriptive-name].md
Examples:
- specs/chore-update-dependencies.md
- specs/bug-fix-login-race-condition.md
- specs/feature-oauth-authentication.md
Always write plans to specs/ directory (or project-specific equivalent).
Match the template's Plan Format exactly - don't add or remove sections.
Date: 2025-12-26 Model: claude-opus-4-5-20251101
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 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.