技能 planning-and-task-breakdown

📦

planning-and-task-breakdown

Name: planning-and-task-breakdown
Author: addyosmani

內容修訂 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)

🥉 78 銅級

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.

你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。

Agent 可讀資源

當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。

Markdown 詳情 GET /skills/addyosmani-planning-and-task-breakdown.md 已簽名 manifest GET /api/skills/addyosmani-planning-and-task-breakdown/manifest 已簽名 lockfile GET /api/skills/addyosmani-planning-and-task-breakdown/lockfile

測試它

正在使用「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.

已掃描檔案

258

分析行數

複核項目

已忽略的誤報

最近一次完成的靜態與語意稽核未偵測到已確認的安全發現。這並不能證明該 Skill 沒有副作用。

審計單位: 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 評分

評分依據證據置信度: 高

架構

可維護性

內容

社群

規範符合度

你可以打造什麼

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 修訂

版本提示

作者未聲明版本。

儲存庫

https://github.com/addyosmani/agent-skills/tree/c004a74784a08295d52749b04cda634125b9a581/skills/planning-and-task-breakdown

引用

5d5054f8a23586f9b500fece1cb613a9dffc787b

維護新鮮度

2026/9/19

使用量

5 次下載 · 0 次瀏覽

檔案結構

📄 SKILL.md