스킬 planning-and-task-breakdown
📦

planning-and-task-breakdown

콘텐츠 리비전 r2 안전 ⚙️ 외부 명령어📁 파일 시스템 접근

Plan Work Into Verifiable Tasks

Large or vague software work can hide dependencies, missing acceptance criteria, and verification gaps. This skill converts a specification into ordered task slices with checkpoints, scope guidance, and clear completion conditions.

지원: Claude Codex Code(CC)
Maintain this Skill? Claim it 🥉 78 브론즈

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청
Review the Skillstore skill "planning-and-task-breakdown" from https://skillstore.io/skills/addyosmani-planning-and-task-breakdown.md and its manifest at https://skillstore.io/api/skills/addyosmani-planning-and-task-breakdown/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

테스트해 보기

"planning-and-task-breakdown" 사용 중입니다. Add email notifications when a user receives a comment.

예상 결과:

  • Task 1: Define notification preferences and the comment event contract. Verify the schema and event payload with focused tests.
  • Task 2: Implement notification delivery for one provider. Verify successful delivery, provider failure handling, and retry behavior.
  • Task 3: Add the user-facing preference flow. Verify that disabled notifications are not sent.
  • Checkpoint: Run the focused test suite and confirm the comment-to-notification flow end to end.

"planning-and-task-breakdown" 사용 중입니다. We need to add search with filters to an existing application.

예상 결과:

The plan separates indexing, the search API, one complete filtered user flow, and later performance work. Each task includes dependencies, acceptance criteria, verification, likely files, and a scope estimate.

보안 감사

안전
v2 • 2026. 9. 19. 버전별 보고서 열기

All 28 static findings are false positives. The flagged backticks, paths, and checklist text are Markdown documentation examples, not executable commands, reconnaissance, or path traversal. No semantic security findings or prompt injection attempts were identified.

1
스캔된 파일
258
분석된 줄 수
0
검토 항목
0
오탐 무시됨
가장 최근에 완료된 정적·의미론적 감사에서 확인된 보안 발견 사항이 감지되지 않았습니다. 이는 스킬에 부작용이 없음을 증명하지 않습니다.
감사자: codex 감사 이력 보기 →
이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기
보안 평가

보고서 링크 복사

https://skillstore.io/skills/addyosmani-planning-and-task-breakdown/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 배지

[![Skillstore security assessment](https://skillstore.io/badges/skills/addyosmani-planning-and-task-breakdown/security.svg)](https://skillstore.io/skills/addyosmani-planning-and-task-breakdown?utm_source=security_passport_badge)

HTML 배지

<a href="https://skillstore.io/skills/addyosmani-planning-and-task-breakdown?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-planning-and-task-breakdown/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

임베드 카드

<iframe src="https://skillstore.io/embed/skills/addyosmani-planning-and-task-breakdown.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
학술 인용 (APA · BibTeX · CFF)

APA 인용

addyosmani. (2026). planning-and-task-breakdown security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-planning-and-task-breakdown/audits/2

BibTeX 인용

@techreport{addyosmani-addyosmani-planning-and-task-breakdown-2026, author = {addyosmani}, title = {planning-and-task-breakdown security audit report (audit version 2)}, institution = {Skillstore}, year = {2026}, number = {2}, url = {https://skillstore.io/skills/addyosmani-planning-and-task-breakdown/audits/2}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "planning-and-task-breakdown security audit report (audit version 2)" version: "unspecified" type: report authors: - name: "addyosmani" date-released: "2026-09-19" url: "https://skillstore.io/skills/addyosmani-planning-and-task-breakdown/audits/2" identifiers: - type: other value: "skillstore:addyosmani-planning-and-task-breakdown:audit:2" description: "Skillstore immutable audit report identifier"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 높음
55
아키텍처
85
유지보수성
87
콘텐츠
67
커뮤니티
83
사양 준수

만들 수 있는 것

Turn a product brief into an implementation plan

Convert a feature brief into ordered tasks with dependencies, acceptance criteria, verification steps, and review checkpoints.

Prepare an agent-ready coding task list

Break a large engineering request into focused vertical slices that an AI coding agent can implement and verify independently.

Coordinate work across contributors

Identify parallel work, shared contracts, sequencing constraints, risks, and the task-list location for a multi-person project.

이 프롬프트를 사용해 보세요

Create a simple task breakdown
Break this request into ordered tasks. For each task, include a short description, acceptance criteria, verification step, dependency, and estimated scope: [paste request].
Map dependencies before implementation
Analyze this specification and map the dependency graph. Then propose a bottom-up task order with one checkpoint after each major phase: [paste specification].
Plan a vertical feature slice
Use vertical slicing to plan this feature. Separate foundation work from complete user flows, identify likely files, define testable acceptance criteria, and flag tasks that are too large: [describe feature and repository context].
Review a plan for delivery risk
Audit the following implementation plan for missing dependencies, unclear acceptance criteria, oversized tasks, weak verification, unsafe parallelization, and missing checkpoints. Return a corrected ordered plan with open questions: [paste plan].

모범 사례

  • Provide the specification, repository conventions, and known constraints before requesting a plan.
  • Require every task to include testable acceptance criteria and a concrete verification step.
  • Review dependencies, checkpoints, scope estimates, and open questions before implementation begins.

피하기

  • Ask for a plan when the change is a single obvious file edit.
  • Accept tasks that say only to implement a feature without acceptance criteria or verification.
  • Parallelize work that changes a shared contract before the contract is defined.

자주 묻는 질문

What input does this skill need?
Provide a specification, goal, constraints, and relevant repository context. More context produces more reliable dependencies and file recommendations.
Does this skill write code?
No. It creates an implementation plan and task list. A separate coding step or agent must implement and test the work.
What is vertical slicing?
Vertical slicing delivers one complete, testable user flow across the needed layers instead of finishing one technical layer at a time.
How are task dependencies handled?
The skill maps prerequisites and orders tasks so foundational contracts and data structures are ready before dependent work begins.
Can the plan use an issue tracker?
Yes. The skill explains how to map task details to an external tracker and record the tracker choice in the plan document.
How should I review the generated plan?
Confirm the requirements, dependencies, acceptance criteria, verification steps, scope estimates, risks, checkpoints, and open questions before implementation.

개발자 세부 정보

작성자

addyosmani

라이선스

MIT

Skillstore 리비전

r2

버전 안내

작성자가 버전을 선언하지 않았습니다.

참조

5d5054f8a23586f9b500fece1cb613a9dffc787b

유지보수 최신성

2026. 9. 19.

사용량

5 다운로드 · 0 조회

파일 구조

📄 SKILL.md

addyosmani의 다른 스킬

전체 보기
전체 보기