append-prd

Convert requirements into dev tasks appended to prd.json.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/nikhilakjoshi/prd-skills --skill append-prd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: append-prd
Source: https://github.com/nikhilakjoshi/prd-skills/tree/main/append-prd
Command: npx skills add https://github.com/nikhilakjoshi/prd-skills --skill append-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert requirements into actionable dev tasks appended to a project's prd.json.

Core Features & Use Cases

  • Break down PRDs, feature specs, raw ideas, or requirements into small, actionable tasks for software delivery.
  • Append tasks to {project}/plans/prd.json to keep planning aligned with execution.
  • Reuse a consistent task schema to support automation, auditing, and tracking.

Quick Start

Provide a PRD or requirements and specify the target project, and the tool will generate and append small tasks to {project}/plans/prd.json.

Frequently Asked Questions about append-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert requirements into actionable development tasks?

To convert requirements into actionable development tasks, provide a PRD or feature spec to generate small JSON task objects. The tool analyzes your repository architecture and appends tasks with categories, descriptions, and steps to plans/prd.json.

What is the best way to break down a PRD for software delivery teams?

The best way to break down a PRD for software delivery is to parse feature specs into a structured JSON array. This process grounds tasks in repository architecture and outputs consistent task objects with category, description, steps, and passes fields.

Can I append raw ideas to an existing prd.json file?

Yes, you can append raw ideas to an existing prd.json file. The tool reads your raw ideas, analyzes the codebase to ground them in architecture, and appends the resulting actionable task objects to the plans/prd.json file.

Does the generated PRD task schema support automation and auditing?

Yes, the generated PRD task schema supports automation and auditing. It reuses a consistent JSON array format with category, description, steps, and passes fields to keep planning aligned with execution and enable tracking.

How do I generate PRD tasks that match my repository architecture?

Generate PRD tasks that match your repository architecture by providing feature specifications to the tool. It reads the requirements and analyzes the repository to ground the resulting task steps and descriptions in your actual architecture.