← ClaudeAtlas

prd-task-creatorlisted

Create a well-written PRD, task, or GitHub issue/sub-issue for a feature, bug, or enhancement. Use when planning work, writing GitHub issues, breaking down epics into sub-issues, or creating local task files. Common prompts: create a task, write a PRD, open a GitHub issue, create a sub-issue, plan this feature, write up this bug, break this down into issues, I want to add X, implement Y.
shipshitdev/skills · ★ 35 · Data & Documents · score 77
Install: claude install-skill shipshitdev/skills
# PRD Task Creator Write a clear, actionable PRD or task — output depends on where the user tracks work. ## Contract Inputs: - Feature, bug, enhancement, or planning request - Destination preference: GitHub issue, local PRD/task file, or both - Optional parent issue, labels, assignee, and priority Outputs: - Draft PRD or task body - Destination-specific create command or file path - Created issue/file URL or path after approval Creates/Modifies: - Local `.agents/memory/<kebab-name>.md` PRD files only after draft approval - GitHub issues/sub-issues only after draft approval External Side Effects: - Reads GitHub issue state - May create GitHub issues, sub-issues, or issue branches Confirmation Required: - Always show the draft before creating files or GitHub issues - Ask before linking sub-issues or creating issue branches Delegates To: - `spec-first` when implementation constraints are still unclear - `tdd` when the work should be executed test-first - `gh-fix-ci` for CI failures after implementation - `roadmap-analyzer` for roadmap-level planning - `cto-advisor` for technical strategy and architecture tradeoffs ## Step 1: Detect workflow preference Check in order: 1. User explicitly says "GitHub issue", "local file", or both 2. Check if `gh auth status` succeeds and a GitHub remote exists → GitHub available 3. If ambiguous, ask: "GitHub issue, local PRD file in `.agents/memory/`, or both?" ## Step 2: Understand the request Ask only what's missing: - What p