Create an Implementation Plan for a Research Task

Create an Implementation Plan for a Research Task

Pipeline mode: This command operates fully autonomously. All decisions are made automatically.

Introduction

Transform research descriptions, estimation problems, or methodological improvements into well-structured plan files that follow project conventions and best practices. This command auto-selects the appropriate detail level based on task complexity.

Research Description

<feature_description> #$ARGUMENTS </feature_description>

If the research description above is empty: Infer the task from recent context — open plan files, recent brainstorms in docs/brainstorms/, or the current estimation code. If no context is available, state "No research task provided" and stop.

0. Idea Refinement

Check for brainstorm output first:

Before analysis, look for recent brainstorm documents in docs/brainstorms/ that match this task:

ls -la docs/brainstorms/*.md 2>/dev/null | head -10

If docs/brainstorms/ does not exist, skip brainstorm lookup and proceed with task analysis.

Relevance criteria: A brainstorm is relevant if:

• The topic (from filename or YAML frontmatter) semantically matches the research description
• Created within the last 14 days
• If multiple candidates match, use the most recent one

If a relevant brainstorm exists:

1. Read the brainstorm document thoroughly — every section matters
2. Announce: "Found brainstorm from [date]: [topic]. Using as foundation for planning."
3. Extract and carry forward ALL of the following into the plan:
   • Key decisions and their rationale
   • Chosen approach and why alternatives were rejected
   • Constraints and requirements discovered during brainstorming
   • Open questions (flag these for resolution during implementation)
   • Success criteria and scope boundaries