Plan With Team

---

description: Creates a concise engineering implementation plan based on user requirements and saves it to specs directory argument-hint: [user prompt] [orchestration prompt] model: opus disallowed-tools: Task, EnterPlanMode hooks: Stop: - hooks: - type: command command: >- uv run $CLAUDE_PROJECT_DIR/.claude/hooks/validators/validate_new_file.py --directory specs --extension .md - type: command command: >- uv run $CLAUDE_PROJECT_DIR/.claude/hooks/validators/validate_file_contains.py --directory specs --extension .md --contains '## Task Description' --contains '## Objective' --contains '## Relevant Files' --contains '## Step by Step Tasks' --contains '## Acceptance Criteria' --contains '## Team Orchestration' --contains '### Team Members'

---

Plan With Team

Create a detailed implementation plan based on the user's requirements provided through the `USER_PROMPT` variable. Analyze the request, think through the implementation approach, and save a comprehensive specification document to `PLAN_OUTPUT_DIRECTORY/.md` that can be used as a blueprint for actual development work. Follow the `Instructions` and work through the `Workflow` to create the plan.

Variables

USER_PROMPT: $1 ORCHESTRATION_PROMPT: $2 - (Optional) Guidance for team assembly, task structure, and execution strategy PLAN_OUTPUT_DIRECTORY: `specs/` TEAM_MEMBERS: `.claude/agents/team/*.md` GENERAL_PURPOSE_AGENT: `general-purpose`

Instructions

• PLANNING ONLY: Do NOT build, write code, or deploy agents. Your only output is a plan document saved to PLAN_OUTPUT_DIRECTORY.
• If no USER_PROMPT is provided, stop and ask the user to provide it.
• If ORCHESTRATION_PROMPT is provided, use it to guide team composition, task granularity, dependency structure, and parallel/sequential decisions.
• Carefully analyze the user's requirements provided in the USER_PROMPT variable
• Determine the task type (chore|feature|refactor|fix|enhancement) and complexity (simple|medium|complex)
• Think deeply (ultrathink) about the best approach to implement the requested functionality or solve the problem
• Understand the codebase directly without subagents to understand existing patterns and architecture
• Follow the Plan Format below to create a comprehensive implementation plan
• Include all required sections and conditional sections based on task type and complexity
• Generate a descriptive, kebab-case filename based on the main topic of the plan
• Save the complete implementation plan to PLAN_OUTPUT_DIRECTORY/.md
• Ensure the plan is detailed enough that another developer could follow it to implement the solution
• Include code examples or pseudo-code where appropriate to clarify complex concepts
• Consider edge cases, error handling, and scalability concern