playbooks

home / skills / shipshitdev / library / task-prd-creator

task-prd-creator skill

/bundles/planning/skills/task-prd-creator

This skill creates structured task files and PRDs for feature requests, then presents them for user approval before implementation.

npx playbooks add skill shipshitdev/library --skill task-prd-creator

Review the files below or copy the command above to add this skill to your agents.

Files (3)
SKILL.md
2.4 KB
---
name: task-prd-creator
description: Use this skill when users request new features, enhancements, bug fixes, or any work that needs planning. Creates structured task files and PRDs (Product Requirements Documents) before implementation. Activates for "I want to add X", "implement Y", "create a task for Z", "plan this feature", or any feature request.
version: 1.0.0
tags:
  - planning
  - task-management
  - prd
  - workflow
  - documentation
  - project-management
auto_activate: true
---

# Task & PRD Creator

## Overview

Create structured task files and PRDs before implementing features. This ensures proper planning, documentation, and clear scope definition.

**CRITICAL RULE:** Never implement a feature without first creating the task + PRD files and getting user approval.

## When This Activates

- "I want to add [feature]"
- "Implement [feature]"
- "Create a task for [feature]"
- "Plan this feature"
- User describes a user story
- Bug that needs tracking

## The Workflow

### Step 1: Understand Request

- **Simple task:** <1 hour, few files
- **Complex feature:** >1 hour, multiple files/systems

### Step 2: Gather Requirements

- Which app/project?
- Priority? (CRITICAL/High/Medium/Low)
- Dependencies?

### Step 3: Check Existing System

- Read architecture docs
- Search for similar implementations

### Step 4: Create Files

**Task file:** `[project]/.agents/TASKS/[task-name].md`
**PRD file:** `[project]/.agents/PRDS/[task-name].md`

### Step 5: Get Approval

Present files, explain approach, **WAIT for user approval**.

## Task File Format

```markdown
## Task: [Feature Name]

**ID:** feature-name-slug
**Label:** [App]: [Feature Name]
**Description:** Brief description
**Type:** Feature | Bug | Enhancement
**Status:** Backlog | To Do | Testing | Done
**Priority:** High | Medium | Low
**Created:** YYYY-MM-DD
**Updated:** YYYY-MM-DD
**PRD:** [Link](../PRDS/feature-name.md)
```

## Critical Rules

1. Create task file
2. Create PRD file
3. Link them together
4. Present to user
5. Get approval
6. Then implement

## Red Flags (Stop and Ask)

- Breaking changes
- Affects multiple projects
- Security implications
- Unclear requirements

## Integration

- `mvp-architect` - MVP scoping
- `planning-assistant` - Content planning
- `agent-folder-init` - Initialize .agents/ structure

---

**For complete PRD template, naming conventions, status update workflow, Context7 integration, and example interactions, see:** `references/full-guide.md`

Overview

This skill creates structured task files and Product Requirements Documents (PRDs) for any new features, enhancements, or bug fixes before implementation. It enforces a planning-first workflow to define scope, priorities, and dependencies. Use it to guarantee clarity, traceability, and user approval before writing code.

How this skill works

When a user requests a feature, enhancement, or bug fix, the skill asks clarifying questions to gather project, priority, and dependency information. It inspects the request complexity and existing project structure, generates a TASKS markdown file and a linked PRD markdown file in the .agents folder, and presents them for user review. The skill halts automation and waits for explicit user approval before any implementation steps.

When to use it

  • User says: 'I want to add X' or 'implement Y'
  • Create a task for a described user story or bug
  • Planning a new feature that needs scoping and acceptance criteria
  • You need to document priority, dependencies, and rollout plan
  • Preparing work items for multiple engineers or teams

Best practices

  • Always create both a TASKS file and a PRD file and link them together
  • Classify work as Simple (<1 hour) or Complex (>1 hour) to set scope
  • Ask about app/project, priority (CRITICAL/High/Medium/Low), and dependencies up front
  • Stop and ask if requirements are unclear, the change breaks backward compatibility, or security is involved
  • Present the files to the requester and explicitly wait for approval before implementing

Example use cases

  • User asks to add a new API endpoint — generate PRD with acceptance criteria and TASKS entry for backend and docs
  • Report of a bug — create a TASKS bug file, link to PRD with reproduction steps and rollback plan
  • Request to enhance a UI flow — produce a PRD with mock scope, success metrics, and testing checklist
  • Planning a cross-project feature — highlight dependencies, affected services, and required migrations
  • Scoping an MVP — integrate with mvp-architect guidance and produce minimum viable deliverables

FAQ

What files does the skill create and where?

It creates a task file in [project]/.agents/TASKS/[task-name].md and a PRD in [project]/.agents/PRDS/[task-name].md, and links them together.

Can implementation begin automatically after file creation?

No. Implementation only proceeds after you review and explicitly approve the generated task and PRD.