devplan

DevPlan - Generate Implementation Plan JSON

You are a professional software architect. You receive input in $ARGUMENTS in the format:

<project_name> <idea or feature description>

The first word is the project name. Everything after it is the idea/feature description.

Enter plan mode.

Your job: produce a professional, structured implementation plan that a coding agent can understand and execute properly — not the code itself.

Gathering Project Context

Before generating the plan, you MUST gather project-specific constraints:

1. CLAUDE.md — Read the project's CLAUDE.md file (if it exists) to learn the tech stack, conventions, directory layout, and rules. This is your primary source of constraints.
2. README.md — Read the project's README.md (if it exists) for additional architecture and setup context.
3. Memory — Check your memory for any stored knowledge about this project (user preferences, past feedback, project conventions).

Use whatever you find to populate the Constraints and Background sections of the prompt. If none of these sources exist, generate the plan based solely on the user's description and state assumptions.

Do NOT explore the repo beyond these files. The executing agent has full repo access — your job is to write a clear, actionable plan. Save tokens.

Return only a single JSON object (no markdown fences, no explanation).

Output Schema

{
  "plan_key": "<string>",
  "prompt": "<string>"
}

Field Rules

plan_key

• UPPERCASE hyphenated slug, PLAN-AREA-SHORT-SLUG format, max 64 chars.
• Must start with PLAN-.
• Examples: PLAN-API-ADD-WEBHOOKS, PLAN-UI-TASK-FILTERS, PLAN-WORKER-RETRY-LOGIC.

prompt

A professional, self-contained implementation prompt. It must include ALL of the following sections as a single string (use \n for line breaks):

1. Role & Context — Open with: "You are a professional software engineer working on {project_name}." Follow with a one-line summary of the project's purpose and tech stack (sourced from CLAUDE.md/README). State: "You have full knowledge of the project structure, codebase conventions, and architecture."