Skip to content
Skills Library
Programming · Planning

task-prd-creator

/task-prd-creator

Use when the user says I want to add X, implement Y, create a task for Z, or plan this feature. Writes a task file plus a PRD under .agent/, links them, and waits for approval before any implementation starts.

Repository
coco ↗
Licence
MIT
Last repository change
25.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when the user says I want to add X, implement Y, create a task for Z, or plan this feature. Writes a task file plus a PRD under .agent/, links them, and waits for approval before any implementation starts.

Original author description

Use when the user says I want to add X, implement Y, create a task for Z, or plan this feature. Writes a task file plus a PRD under .agent/, links them, and waits for approval before any implementation starts.

How it works

  1. Overview
  2. When This Activates
  3. The Workflow
  4. Task File Format
  5. Critical Rules
  6. Red Flags (Stop and Ask)
  7. Integration
Original SKILL.md headings · 86 lines, 274 words
SKILL.md preview
---
name: task-prd-creator
description: "Use when the user says I want to add X, implement Y, create a task for Z, or plan this feature. Writes a task file plus a PRD under .agent/, links them, and waits for approval before any implementation starts."
version: 1.0.0
tags:
  - planning
  - task-management
  - prd
  - workflow
  - documentation
  - project-management
auto_activate: true
domain: pm
---

# 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]/.agent/TASKS/[task-name].md`
**PRD file:** `[project]/.agent/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

- `writing-plans` - Implementation plan authoring
- `prd-generator` - Heavier PRD generation and validation

---

**For complete PRD template, naming conventions, status update workflow, Context7 integration, and example interactions, see:** `references/full-guide.md`
Files in this package (3)
  • SKILL.md 2 KB
  • plugin.json 1 KB
  • references/full-guide.md 10 KB

Versions

The database has no other skills named task-prd-creator.

Database snapshot: 13.11.2026 · package version 10ce4186ebd2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100plan
    Create a detailed implementation plan for a feature or task. Use when user wants to plan before coding.
  • 100writing-feature-prds
    Use when starting a new feature, defining requirements before implementation, or when the user says "new feature", "create a spec", "create a PRD", or "feature PRD".
  • 100create-prd
    Create a product requirement document (PRD) for a new feature. Use when the user wants to create a new feature, plan a feature, or write a PRD.
  • 100add-task
    Create a new task file following the taskmd specification. Use when the user wants to add a new task to the project.
  • 100add-task
    Create a new task file following the taskmd specification. Use when the user wants to add a new task to the project.
  • 100create-prd
    This skill should be used when the user asks to "create PRD", "write product requirements document", or mentions "PRD", "product requirements document".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.