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

task-review

스타2

포크0

업데이트2026년 4월 15일 18:01

Reviews a completed task for code quality, spec adherence, and test coverage. Use after a task has been implemented via run-task. Don't use for full code review, QA, or implementation.

설치

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

Manus에서 실행

출처

raphaelsasso

raphaelsasso/sdd-nestjs-svelte-boilerplate

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

다운로드

Manus에서 실행

Task Review

Step 0: Verify Dependencies

Identify the target feature folder (tasks/prd-[feature]/) and the task number.
Verify the following files exist:
- tasks/prd-[feature]/N_task.md (the completed task)
- tasks/prd-[feature]/techspec.md
For each missing file, warn the user: "[WARNING] File not found: ."
- Task file: "The task file is needed to validate what was implemented."
- TechSpec: "Without the TechSpec, the review cannot verify architectural compliance."
Ask the user: "Would you like to continue the review without this artifact?" (use the ask user question tool).
If the task file itself is missing, recommend aborting.

Step 1: Analyze Changes

Read the completed task file to understand what was implemented.
Read the Tech Spec for architectural context.
Use git diff or git log to identify the code changes made for this task.

Step 2: Review

Verify task requirements are met:
- All subtasks marked as complete
- Success criteria from the task file are satisfied
Check code quality:
- Follows project conventions (CLAUDE.md)
- No workarounds or hacks
- Proper error handling and types
Verify tests:
- Tests exist for the implemented functionality
- Tests cover the scenarios defined in the task
- All tests pass

Step 3: Produce Review Artifact

Generate a review report covering:
- Summary: Pass / Needs Changes
- Compliance: Task requirements met?
- Code Quality: Issues or suggestions
- Tests: Coverage and quality
- Required Actions: Required fixes (if any)
Write the report to tasks/prd-[feature]/N_task_review.md.

Error Handling

If the task is not marked as complete in tasks.md, warn the user before reviewing.
If tests are failing, list the failures and mark the review as "needs changes."

이 저장소의 다른 Skills

같은 저장소

create-prd

raphaelsasso/sdd-nestjs-svelte-boilerplate

Generates a Product Requirements Document (PRD) from a feature prompt. Use when planning a new feature, starting a project, or when asked to create a PRD. Don't use for technical specifications, task breakdowns, or implementation.

2026-04-152

create-tasks

raphaelsasso/sdd-nestjs-svelte-boilerplate

Breaks down a PRD and Tech Spec into an ordered list of implementable tasks. Use when PRD and Tech Spec are ready and the next step is planning the implementation sequence. Don't use for creating PRDs, writing specs, or implementing code.

2026-04-152

create-techspec

raphaelsasso/sdd-nestjs-svelte-boilerplate

Generates a Technical Specification from an existing PRD. Use when a PRD is ready and the next step is to define architecture, APIs, data models, and implementation strategy. Don't use for requirements gathering, task breakdown, or implementation.

2026-04-152

run-bugfix

raphaelsasso/sdd-nestjs-svelte-boilerplate

Fixes all bugs listed in a bugs.md file with root-cause analysis and regression tests. Use after QA has identified bugs that need fixing. Don't use for new features, code review, or QA testing.

2026-04-152

run-qa

raphaelsasso/sdd-nestjs-svelte-boilerplate

Performs Quality Assurance on implemented features including E2E testing, accessibility checks, and requirements verification. Use after implementation and code review are done. Don't use for code review, implementation, or bug fixing.

2026-04-152

run-review

raphaelsasso/sdd-nestjs-svelte-boilerplate

Performs a structured code review of implemented features against the PRD and Tech Spec. Use after tasks are implemented and code needs quality validation. Don't use for QA testing, bug fixing, or implementation.

2026-04-152

name	task-review
description	Reviews a completed task for code quality, spec adherence, and test coverage. Use after a task has been implemented via run-task. Don't use for full code review, QA, or implementation.

Task Review

Step 0: Verify Dependencies

Identify the target feature folder (tasks/prd-[feature]/) and the task number.
Verify the following files exist:
- tasks/prd-[feature]/N_task.md (the completed task)
- tasks/prd-[feature]/techspec.md
For each missing file, warn the user: "[WARNING] File not found: ."
- Task file: "The task file is needed to validate what was implemented."
- TechSpec: "Without the TechSpec, the review cannot verify architectural compliance."
Ask the user: "Would you like to continue the review without this artifact?" (use the ask user question tool).
If the task file itself is missing, recommend aborting.

Step 1: Analyze Changes

Read the completed task file to understand what was implemented.
Read the Tech Spec for architectural context.
Use git diff or git log to identify the code changes made for this task.

Step 2: Review

Verify task requirements are met:
- All subtasks marked as complete
- Success criteria from the task file are satisfied
Check code quality:
- Follows project conventions (CLAUDE.md)
- No workarounds or hacks
- Proper error handling and types
Verify tests:
- Tests exist for the implemented functionality
- Tests cover the scenarios defined in the task
- All tests pass

Step 3: Produce Review Artifact

Generate a review report covering:
- Summary: Pass / Needs Changes
- Compliance: Task requirements met?
- Code Quality: Issues or suggestions
- Tests: Coverage and quality
- Required Actions: Required fixes (if any)
Write the report to tasks/prd-[feature]/N_task_review.md.

Error Handling

If the task is not marked as complete in tasks.md, warn the user before reviewing.
If tests are failing, list the failures and mark the review as "needs changes."