القائمة
Break an issue file into concrete, ordered, AI-executable tasks. Use when the user wants to implement an issue, start work on a ticket, or break down an issue into smaller steps.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Convert a project complexity diagnosis into a practical intervention plan. Use after project-complexity-mapper, especially when the user provides a TOE findings table, quadrant chart, hotspot quadrants, management-fit table, or handoff table and wants actions, interventions, sequencing, owners, or next steps.
Diagnose project complexity from a rough project description using the DelftX TOE framework and detail/dynamic complexity model. Use when the user wants to map, score, visualize, or understand project complexity; create a TOE matrix; generate a quadrant chart; or choose a fit-for-purpose management approach.
Perform a language-agnostic first-pass code review covering logic errors, bad practices, operation ordering, magic strings, pattern improvements, strict type checking, and SQL injection. Use when asked to review code, audit a file, or check a diff. Accepts a single file, a diff with multiple hunks, or can explore the repo when needed to resolve external references. If no input is provided, ask the user to share a file or diff before proceeding.
Run a cross-cutting audit across all code produced for a feature. Use when a feature is complete, all PRs are merged, and the user wants a final review for security issues, logic errors, consistency, and best practices.
Break a PRD into independently-grabbable issues using tracer-bullet vertical slices. Use when the user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
Create a PRD through user interview, codebase exploration, and module design, then save it as a file. Use when the user wants to write a PRD, create a product requirements document, or plan a new feature.
| name | issues-to-tasks |
| description | Break an issue file into concrete, ordered, AI-executable tasks. Use when the user wants to implement an issue, start work on a ticket, or break down an issue into smaller steps. |
Break a single vertical-slice issue into concrete, ordered tasks that can each be completed in one focused AI session.
Ask the user for the issue. If not provided, ask for the issue number or URL or file. Read the parent PRD issue referenced in the "Parent PRD" field.
Explore the parts of the codebase touched by this issue. Focus on:
Break the issue into ordered tasks. Each task must:
Label each task with its type:
Prefer WRITE and TEST tasks interleaved over a block of WRITE followed by a block of TEST.
Present the proposed task list as a numbered list. For each task show:
user_id column to sessions table")Ask the user:
Iterate until the user approves the list.
Save the approved task list to a file in the format and location specified by the user.
Use the task file template below.
# Tasks for #:Parent issue: # Parent PRD: #
Type: WRITE / TEST / MIGRATE / CONFIG / REVIEW
Output:
Depends on: <task numbers or "none">
<A short paragraph describing exactly what to do. Written as an instruction to the AI that will execute it. Include: which files to touch, which pattern to follow, which existing code to use as reference. Do NOT include code snippets — describe intent, not implementation.>
Do NOT modify the parent issue or the parent PRD.