Menü
Break down a PRD into tasks following the task YAML spec
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
This skill should be used when the user needs to automate browser interactions, test UI workflows, verify page elements, take screenshots, upload files to forms, or interact with web applications during development and debugging. Use this skill for testing PDF upload dialogs, form interactions, dropdown selections, and visual verification of web pages.
Execute tasks from a tasks.yaml by orchestrating code-writer agents
Plan a feature using the prd-planner subagent
Manage tmux sessions, windows, and panes from the CLI — list state, read pane output, send keys/commands, create or kill sessions and windows, and inspect long-running terminal work. Use this skill whenever the user mentions tmux, asks to check what's running in another terminal, wants to start a background process in a tmux session, send a command to a running pane, capture or tail output from a tmux pane, attach context from a pane, or troubleshoot a stuck tmux process — even if they don't explicitly say "tmux command."
Plan a feature using the prd-planner subagent
Domain-Driven Design + Ports & Adapters (Hexagonal Architecture) implementation guide. Use this skill whenever the user invokes /ddd, asks to build a feature using DDD, wants to model a domain, design bounded contexts, implement hexagonal architecture, or review code for DDD compliance. Also trigger when the user mentions entities, value objects, aggregates, repositories, domain events, use cases, ports, adapters, or composition root in an architectural context.
Basierend auf der SOC-Berufsklassifikation
| name | tasks |
| description | Break down a PRD into tasks following the task YAML spec |
| argument-hint | <prd-path-or-description> [--name <feature-name>] |
Break down a PRD into actionable tasks with dependencies following the task YAML spec.
/tasks [--name ]
prd-path-or-description: Either a file path to a PRD markdown file, or a description string (required)--name: Optional feature name (auto-generated from first 4 words if not provided)/tasks prd/authentication/prd.md /tasks "Build user authentication with OAuth2 and JWT" /tasks ./features/search.md --name search-feature /tasks "Add real-time notifications with websockets" --name realtime-notif
Parse input:
Generate feature name if not provided:
Invoke the prd-planner subagent with:
The prd-planner executes 3 phases:
tasks:
- key: task-name # Unique kebab-case identifier
description: Brief description of the task
details: ./task-name.md # Path to detail file with implementation notes
status: open # open, progress, or done
depends: [] # List of task keys this depends on
✓ Tasks created: prd/{feature-name}/
- prd.md
- tasks.yaml (X tasks)
- {X} detail files
Tasks:
1. task-name-1 (no deps)
2. task-name-2 (depends: task-name-1)
...
Manage tasks.yaml with uv run ~/.claude/skills/tasks/tasks.py (view status, CRUD on tasks) or run /code <tasks.yaml> to execute ready tasks.
tasks.py resolves the YAML path relative to the current working directory. Before invoking it, run pwd and pass a path that resolves from there — do NOT prepend packages/<x>/ if your shell is already inside that package. Example failure: running uv run ~/.claude/skills/tasks/tasks.py packages/stamp/prds/foo/tasks.yaml summary from packages/stamp/ fails with FileNotFoundError because it expands to packages/stamp/packages/stamp/prds/foo/tasks.yaml. Use prds/foo/tasks.yaml instead.