원클릭으로 Manus에서 모든 스킬 실행

create-tasks

스타0

포크1

업데이트2026년 5월 21일 01:47

Create implementation task plans and task files from complete PRDs and TechSpecs. Use when Codex is asked to create, draft, generate, or save tasks; break a PRD and technical specification into deliverable implementation tasks; define subtasks, success criteria, test requirements, relevant files, rule conformance, or skill conformance; or create files under tasks/prd-[feature-name]/tasks.md and tasks/prd-[feature-name]/[num]_task.md.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

rodrigobranas

rodrigobranas/aidev_axon_7

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Create Tasks

Core Workflow

Use this skill to turn an existing PRD and TechSpec into approved, implementation-ready task files saved in the project task structure.

Read resources/create-tasks.md before starting. Treat that file as the canonical workflow for this skill.

Load resources/task-list-template.md only when creating tasks.md. Load resources/task-template.md only when creating individual task files. Treat both files as the required task template standards.

Execution Rules

Confirm and read the PRD at tasks/prd-[feature-name]/prd.md.
Confirm and read the TechSpec at tasks/prd-[feature-name]/techspec.md.
Analyze requirements, technical decisions, relevant project rules, and relevant project skills.
Before generating any files, show the high-level task list to the user for approval.
Do not implement code.
Make each main task a well-defined deliverable.
Include unit and integration tests for every main task; include E2E tests where applicable.
Generate tasks.md from the exact template in resources/task-list-template.md.
Generate each [num]_task.md from the exact template in resources/task-template.md.
Save files under tasks/prd-[feature-name]/.
Report the generated file paths and wait for confirmation before any implementation begins.

Expected Inputs

Typical input is a PRD/TechSpec directory, feature name, or request such as:

"Use $create-tasks for tasks/prd-team-invitations."
"Create implementation tasks for the checkout-flow PRD and TechSpec."
"Generate task files from this PRD and technical specification."

If the feature directory is unclear, inspect tasks/prd-* directories and ask for clarification only when multiple plausible feature folders exist.

이 저장소의 다른 Skills

같은 저장소

create-prd

rodrigobranas/aidev_axon_7

Create Product Requirements Documents (PRDs) from feature requests using a required clarify-plan-draft-save workflow. Use when Codex is asked to write, generate, create, draft, or update a PRD, product requirements document, product spec, feature requirements document, or requirements artifact that should be saved as tasks/prd-[feature-name]/prd.md.

2026-05-210

create-tasks

rodrigobranas/aidev_axon_7

Create implementation task lists and individual task files from an existing PRD and Tech Spec. Use when Codex is asked to write, generate, create, draft, or update feature tasks, implementation tasks, task breakdowns, delivery plans, or task files based on tasks/prd-[feature-name]/prd.md and tasks/prd-[feature-name]/techspec.md.

2026-05-210

create-techspec

rodrigobranas/aidev_axon_7

Create implementation-ready Technical Specifications from existing PRDs using a required analyze-research-clarify-draft-save workflow. Use when Codex is asked to write, generate, create, draft, or update a Tech Spec, technical specification, implementation specification, architecture spec, or engineering plan based on tasks/prd-[feature-name]/prd.md and save it as tasks/prd-[feature-name]/techspec.md.

2026-05-210

execute-bugfix

rodrigobranas/aidev_axon_7

Fix documented QA bugs for a feature by reading bugs.md, qa.md, PRD, Tech Spec, and tasks; planning fixes by severity; implementing root-cause fixes; adding regression tests; validating with project tests and Playwright for UI bugs; and updating bugfix artifacts. Use when Codex is asked to fix bugs, resolve QA findings, address failed QA, or complete bugfix work in tasks/prd-[feature-name]/.

2026-05-210

execute-qa

rodrigobranas/aidev_axon_7

Execute QA validation for a completed feature against its PRD, Tech Spec, and tasks using Playwright MCP, accessibility checks, visual review, bug documentation, and a final QA report. Use when Codex is asked to test, QA, validate, approve, reject, or verify a feature implementation in tasks/prd-[feature-name]/.

2026-05-210

execute-review

rodrigobranas/aidev_axon_7

Execute a code review for implemented work by analyzing git diff, reading modified files, checking project rules and skills, verifying Tech Spec and task adherence, running tests, identifying code quality issues, and saving a code review report. Use when Codex is asked to review code, validate implementation quality, approve changes, or produce codereview.md for a feature or project change.

2026-05-210

name

create-tasks

description

Create Tasks

Core Workflow

Use this skill to turn an existing PRD and TechSpec into approved, implementation-ready task files saved in the project task structure.

Read resources/create-tasks.md before starting. Treat that file as the canonical workflow for this skill.

Execution Rules

Confirm and read the PRD at tasks/prd-[feature-name]/prd.md.
Confirm and read the TechSpec at tasks/prd-[feature-name]/techspec.md.
Analyze requirements, technical decisions, relevant project rules, and relevant project skills.
Before generating any files, show the high-level task list to the user for approval.
Do not implement code.
Make each main task a well-defined deliverable.
Include unit and integration tests for every main task; include E2E tests where applicable.
Generate tasks.md from the exact template in resources/task-list-template.md.
Generate each [num]_task.md from the exact template in resources/task-template.md.
Save files under tasks/prd-[feature-name]/.
Report the generated file paths and wait for confirmation before any implementation begins.

Expected Inputs

Typical input is a PRD/TechSpec directory, feature name, or request such as:

"Use $create-tasks for tasks/prd-team-invitations."
"Create implementation tasks for the checkout-flow PRD and TechSpec."
"Generate task files from this PRD and technical specification."

If the feature directory is unclear, inspect tasks/prd-* directories and ask for clarification only when multiple plausible feature folders exist.