# Generate

Phase 2 of the prd-taskmaster pipeline: spec generation and task parsing.

- Repository: https://github.com/anombyte93/prd-taskmaster (606 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-08-14
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add anombyte93/prd-taskmaster --skill generate -g -a claude-code -y`
Codex: `npx skills add anombyte93/prd-taskmaster --skill generate -g -a codex -y`
Cursor: `npx skills add anombyte93/prd-taskmaster --skill generate -g -a cursor -y`
Gemini CLI: `npx skills add anombyte93/prd-taskmaster --skill generate -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add anombyte93/prd-taskmaster`

## Description

Phase 2 of the prd-taskmaster pipeline: spec generation and task parsing. Loads a template (comprehensive|minimal), fills it with DISCOVER-phase constraints and answers, validates the spec (placeholders_found, grade thresholds), parses the PRD into tasks via task-master, runs TaskMaster's native complexity analysis, and expands every task into verifiable subtasks. Autonomous-safe. Declares GENERATE complete so HANDOFF can follow.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Phase 2: Generate

Declarative phase skill. Invoked by the prd-taskmaster orchestrator when
`current_phase` is `GENERATE`. Never called directly by a user.

The one rule: **generate the spec, validate it catches placeholders, parse it
into tasks, expand every task into subtasks. Quality over speed.**

## Entry gate

1. Call `mcp__plugin_prd_go__check_gate(phase="GENERATE", evidence={})` for diagnostics.

   `check_gate` is an EXIT gate: it checks `task_count > 0`, `subtask_coverage >= 1.0`,
   and `validation_grade in (EXCELLENT, GOOD)`, all of which are GENERATE's OWN OUTPUTS,
   i.e. evidence to *advance*, not preconditions to *enter*. On first entry none exist
   yet, so a `gate_passed: false` here is EXPECTED, the state machine's legal
   transitions already guarantee only legal entry.

   - **First entry** (no evidence yet): note the result and continue with the Procedure.
   - **Re-entry**: if the gate reports violations, report them and stop, it protects
     against re-running a completed phase or skipping ahead from DISCOVER.
2. Read the DISCOVER output (discovery summary + `CONSTRAINTS CAPTURED` block
   + scale classification). If any of these are missing, report and stop, the
   gate should have caught this, but belt-and-braces.

## Generate checklist

Copy into your response before running the procedure:

```
GENERATE CHECKLIST:
- [ ] Template loaded (comprehensive|minimal)
- [ ] Spec written with discovery answers (no bare placeholders remaining)
- [ ] CONSTRAINT CHECK: every DISCOVER constraint appears in the spec
- [ ] SCOPE CHECK: task count matches scale (Solo 8-12, Team 12-20, Enterprise 20-30)
- [ ] Validation score: ___ / ___ (grade: ___)
- [ ] placeholders_found: ___ (bare placeholders = 0 required)
- [ ] Warnings addressed or acknowledged
- [ ] Tasks parsed: ___ tasks created
- [ ] Complexity analyzed via TaskMaster: Y/N
- [ ] All tasks expanded into subtasks: Y/N
```

## Step 1: Choose and load template

The rest: https://github.com/anombyte93/prd-taskmaster/blob/HEAD/skills/generate/SKILL.md