Skills planning-and-task-breakdown
๐Ÿ“ฆ

planning-and-task-breakdown

Content revision r2 Safe โš™๏ธ External commands๐Ÿ“ Filesystem access

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.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
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.

Your Agent should still show its plan and request any confirmation required by the security policy.

Test it

Using "planning-and-task-breakdown". Add email notifications when a user receives a comment.

Expected outcome:

  • 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.

Using "planning-and-task-breakdown". We need to add search with filters to an existing application.

Expected outcome:

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.

Security Audit

Safe
v2 โ€ข 9/19/2026 Open versioned report

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
Files scanned
258
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

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

Markdown badge

[![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 badge

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

Embed card

<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>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

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 citation

@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 Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
67
Community
83
Spec Compliance

What You Can Build

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.

Try These Prompts

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].

Best Practices

  • 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.

Avoid

  • 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.

Frequently Asked Questions

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.

Developer Details

Author

addyosmani

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

5d5054f8a23586f9b500fece1cb613a9dffc787b

Maintenance freshness

9/19/2026

Usage

5 downloads ยท 0 views

File structure

๐Ÿ“„ SKILL.md

More from addyosmani

View all
View all