Skip to content

Instantly share code, notes, and snippets.

@nicovalencia
Created February 19, 2026 21:59
Show Gist options
  • Select an option

  • Save nicovalencia/212f41cb53b5db384421befb56d19c3e to your computer and use it in GitHub Desktop.

Select an option

Save nicovalencia/212f41cb53b5db384421befb56d19c3e to your computer and use it in GitHub Desktop.
Claude Code /pi skill - Plan and research implementation

Plan and research implementation for: $ARGUMENTS

Execution Steps

Step 1: Internal Codebase Research Phase

Launch a single researcher agent for codebase-only research (no external research):

Codebase Research: Use Task tool with subagent_type="researcher" with this prompt: "Explore this codebase to understand how to implement: $ARGUMENTS

Research:

  • Check docs/ directory for relevant documentation files
  • Existing patterns, components, and utilities relevant to this task
  • Files that will need modification or serve as references
  • Current conventions and best practices in this codebase
  • Architectural constraints or considerations

Return a concise summary with:

  • Relevant documentation from docs/ if found
  • Related codebase parts with file:line references
  • Best practices observed in existing code
  • Key files and steps to consider for implementation"

Step 2: Architecture Phase

After the research agent completes, launch an architect agent using Task tool with subagent_type="architect". Provide:

  • Original task: $ARGUMENTS
  • Codebase research results

Instruct architect to write a markdown implementation plan in the project's plans/ directory (create if needed). The plan filename should be kebab-case based on the feature name.

Plan must include:

  1. Brief Summary - Short overview of what will be built
  2. User Actions Required - Manual steps needed (dependencies, env vars, external setup)
  3. File Change Diagram - ASCII or markdown representation of files to create/modify
  4. Implementation Phases - Detailed step-by-step instructions in logical phases

Plan must NOT include:

  • Timelines or estimates
  • Future considerations
  • Alternative suggestions
  • Possible improvements

Write only the single best definitive implementation approach.

Step 3: Confirm Completion

Report the plan file path to the user when complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment