Prd Creator

# Implementation Task Generation

Transform the completed PRD into simple, concise, actionable and verifiable implementation tasks in JSON format. This creates a comprehensive task list for developers (human or AI) to build and verify the product.

## When to Use

After completing PRD creation, ask the user:
"Your PRD is complete. Would you like me to generate implementation tasks? I'll create a comprehensive JSON task list that breaks down all features into verifiable development work."

Only proceed after user confirmation.

## Task Generation Workflow

You should read the PRD markdown file located in `PROJECT_ROOT/.agent/prd/PRD.md`.
Each task in the PRD will have a unique ID, formatted as `TASK-${ID}`.
Use those IDs to generate the task list, except `TASK-1` is always reserved for prerequisite verification.

Copy and track progress:

```
Task Generation Progress:
- [ ] Analyze the complete PRD
- [ ] Generate mandatory prerequisite verification task first
- [ ] Generate task index in `PROJECT_ROOT/.agent/tasks.json`
- [ ] Generate detailed spec for each task in `PROJECT_ROOT/.agent/tasks/TASK-${ID}.json`
- [ ] Present complete task list to user for review
```

**CRITICAL**: If any of the tasks is unclear, interview the user relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide the user's recommended answer. Ask the questions one at a time.
If a question can be answered by exploring the codebase, explore the codebase instead.

## Mandatory First Task: Prerequisite Verification

Every generated task list must start with `TASK-1: Verify project prerequisites and access`.

Use the `Prerequisites and Access` section from `PROJECT_ROOT/.agent/prd/PRD.md` as the source of truth. This task must verify that implementation can safely begin before feature work starts.

`TASK-1` must confirm:
- `PROJECT_ROOT/.env.local` exists and contains placeholder entries for every required environment variable name from the PRD
- The user has manually filled real local values where needed, without copying those values into the PRD, task specs, logs, or chat
- Database access can be verified or the missing access is explicitly recorded
- Required MCP servers/tools are available and authenticated, or gaps are explicitly recorded
- Required service documentation links are available and relevant
- Required login/test users exist or there are clear steps to create/request them
- Any open prerequisite gaps have a user-approved proceed/block decision from the PRD

All downstream implementation tasks that require these prerequisites must include `TASK-1` in `dependencies`.

Use this exact shape for the first task, adapting names and details to the PRD:

```json:PROJECT_ROOT/.agent/tasks/TASK-1.json
{
  "id": "TASK-1",
  "title": "Verify project prerequisites and access",
  "category": "setup",
  "description": "Verify that required database access, MCPs, service documentation, environment variables, and login/test users are available before implementation begins.",
  "acceptanceCriteria": [
    "`PROJECT_ROOT/.env.local` exists with placeholder entries for every required environment variable name listed in the PRD",
    "Real secret values are not written to the PRD, task specs, repository, logs, or chat",
    "The user has manually filled required local secret values in `.env.local` where needed",
    "Database connectivity is verified, or the missing access is recorded with a user-approved proceed/block decision",
    "Required MCP servers/tools are installed and authenticated, or gaps are recorded with a user-approved proceed/block decision",
    "Required service documentation links are available to the implementer",
    "Required login/test users are available or documented with request/create steps, without passwords or secret values"
  ],
  "steps": [
    {
      "step": 1,
      "description": "Rea