agent-prompts

To turn a PRD into structured tasks, this skill transforms product requirements and acceptance criteria into machine-parseable TASKS.json and human-readable TASKS.md files. It maps your high-level features into phase-based planning structures and prompt templates for automated execution.

The best way to generate machine-parseable task manifests from an SDD is to use an automated planning tool that outputs structured JSON schemas. This skill parses your software design documents to create a TASKS.json file capturing metadata for agent orchestration.

Yes, you can use a PRD to generate both developer documentation and agent execution prompts simultaneously. This skill produces a human-readable TASKS.md view for team reviews alongside the TASKS.json file containing explicit prompt templates for autonomous agents.

Converting product requirements into phase-based planning works by extracting features and acceptance criteria from your PRD or SDD and mapping them into structured task sequences. This creates an end-to-end implementation plan with explicit testing steps and prompt templates.

You do not need to manually structure acceptance criteria for automated task generation if your PRD or SDD already outlines them. The skill automatically maps your provided requirements into explicit acceptance criteria and testing steps within the generated task manifests.

Generating a TASKS.json file from product requirements ensures machine-parseable task metadata for seamless agent orchestration. It eliminates manual formatting errors by automatically structuring phase-based planning, acceptance criteria, and prompt templates directly from your PRD or SDD inputs.