generate

Solid

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.

AI & Automation 508 stars 52 forks Updated today MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
90
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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={})`. If the call returns `{gate_passed: false, violations: [...]}`, report the violations and stop. The gate protects against re-entering a completed phase or skipping ahead from DISCOVER. **Known issue (Mum dogfood feedback [10] — WORST):** check_gate(GENERATE) currently checks `task_count > 0`, `subtask_coverage >= 1.0`, and `validation_grade in (EXCELLENT, GOOD)` — all of which are GENERATE's OWN OUTPUTS, not entry preconditions. First-time entry deadlocks. State machine LEGAL_TRANSITIONS already prevents illegal entry — proceed past this gate on first entry. Semantic fix in flight (see morning brief). 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 DISCOV...

Details

Author
anombyte93
Repository
anombyte93/prd-taskmaster
Created
7 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

discover

Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

508 Updated today
anombyte93
AI & Automation Solid

handoff

Phase 3 of the prd-taskmaster pipeline: smart mode selection and user handoff. Detects installed capabilities (superpowers, ralph-loop, task-master-ai, playwright, research providers), recommends ONE execution mode (A/B/C) with reasoned justification, appends the task-execution workflow to CLAUDE.md, surfaces a structured AskUserQuestion multi-option picker for user agency, and dispatches the chosen mode. Mode D (Atlas Fleet) is selectable only when detect_capabilities returns tier=premium (licensed atlas-launcher detected); otherwise it is a locked Atlas Pro teaser. Plan Mode is NOT used (spec section 13.5): AskUserQuestion is the sole user-agency mechanism. Declares HANDOFF complete so EXECUTE can follow.

508 Updated today
anombyte93
Code & Development Listed

prd-taskmaster

PRD generator that creates comprehensive requirements, publishes as a GitHub issue, and triggers /agent-os:shape-spec for orchestrated execution. No deferred scope — every requirement is a must-deliver. Use when user requests "PRD", "product requirements", or wants to plan a feature for implementation.

0 Updated 2 months ago
bzellman