planning-and-task-breakdown
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.
Установить с помощью моего Агента
Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу 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-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «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.
Аудит безопасности
Безопасно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.
Факторы риска
⚙️ Внешние команды (25)
📁 Доступ к файловой системе (1)
Поделиться и цитировать этот отчет
Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. 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
[](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.
Попробуйте эти промпты
Break this request into ordered tasks. For each task, include a short description, acceptance criteria, verification step, dependency, and estimated scope: [paste request].
Analyze this specification and map the dependency graph. Then propose a bottom-up task order with one checkpoint after each major phase: [paste specification].
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].
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?
Does this skill write code?
What is vertical slicing?
How are task dependencies handled?
Can the plan use an issue tracker?
How should I review the generated plan?
Сведения для разработчиков
Автор
addyosmaniЛицензия
MIT
Ревизия Skillstore
r2
Примечание о версии
Автор не указал версию.
Ссылка
5d5054f8a23586f9b500fece1cb613a9dffc787b
Актуальность поддержки
19.09.2026
Использование
5 загрузок · 0 просмотров
Структура файлов
📄 SKILL.md