القائمة
Break down a PRD into actionable tasks with dependencies, written to tasks.yaml. Use when the user wants to convert a PRD or feature description into trackable tasks.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Hand off the current task to a fresh background agent running in its own workmux worktree, passing a self-contained prompt synthesized from this conversation's context. Use when the user wants to outsource, delegate, or "hand off" implementation work to a separate agent session (e.g. "handoff this fix", "outsource it to a ccd agent", "spin up an agent to do X").
Delegate a code review to pi (`pi /skill:review`) running in a tmux window, then dispatch subagents to fix each finding and check it off the review file. Use when the user wants an automated review-and-fix loop over their current changes.
Teach a topic using the Feynman technique — explain simply, have the user re-explain, identify gaps, re-teach, and loop until they can explain it on their own. Use when the user wants to deeply understand a topic, test their understanding, or mentions "Feynman".
Build a focused 20-hour learning plan for a topic, structured as 10 two-hour sessions following the Pareto principle (20% that drives 80% of results). Use when the user wants to learn a topic fast, build a study plan, or create a structured curriculum.
Create or update a GitHub pull request for the current branch, committing pending changes first. Use when the user wants to open a PR, update an existing PR, or ship a branch for review.
Ask questions about specific GitHub code repositories using DeepWiki. Use when the user asks about a repo's code, architecture, configuration, modules, APIs, examples, or behavior and provides a GitHub repository in owner/repo form or as a GitHub URL.
| name | tasks |
| description | Break down a PRD into actionable tasks with dependencies, written to tasks.yaml. Use when the user wants to convert a PRD or feature description into trackable tasks. |
| 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.