搜索
搜索结果
34 results for "planning and task breakdown"
planning-and-task-breakdown
将工作分解为有序的任务。当你有规范或明确的需求，需要将工作分解为可实施的任务时使用。当任务感觉太大无法开始、需要估算范围或可以并行工作时使用。
addyosmani
plan-writing
Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.
sickn33
breakdown-test
测试规划与质量保证提示，用于生成针对GitHub项目的全面测试策略、任务分解和质量验证计划。
github
fusion-skills
Entrypoint for all Fusion skill lifecycle operations. USE FOR: finding, installing, updating, syncing, or greenkeeping skills; setting up skill automation; creating or authoring a new skill; reporting a bug with a skill. DO NOT USE FOR: resolving GitHub issues, reviewing PRs, planning task breakdowns, or authoring GitHub issues — those are handled by other Fusion skills.
equinor
plan-task
Refine a draft task specification into a fully planned, implementation-ready task with acceptance criteria, architecture, per-step sub-task files and verifiable phases
neolabhq
brief-to-tasks
将设计简报分解为按顺序排列的可独立构建的任务清单，采用垂直切片方式。保存为 Markdown 格式的清单。当用户想要分解工作、从简报创建任务、规划实现顺序或提到“任务”或“分解”时使用。
julianoczkowskifusion-issue-task-planning
Plan and break down user-story issues into ordered, traceable task issue drafts with explicit publish gates.
equinor
planning-with-files-zh
基于 Manus 风格的文件规划系统，用于组织和跟踪复杂任务的进度。创建 task_plan.md、findings.md 和 progress.md 三个文件。当用户要求规划、拆解或组织多步骤项目、研究任务或需要超过5次工具调用的工作时使用。支持 /clear 后的自动会话恢复。触发词：任务规划、项目计划、制定计划、分解任务、多步骤规划、进度跟踪、文件规划、帮我规划、拆解项目
othmanadi
create-plan
実装タスクの計画を `_/local-plans/<plan-name>.md` に作成する。「計画立てて」「設計して」「実装方針を考えて」「タスク分解して」で使用。 Explore Agent でコードベースを先に調査し、検証可能な粒度・並列実行可能な単位で記述する。 plan-verifier Agent で検証可能な標準フォーマット（背景・現状・設計・ファイル構成ツリー・実装ステップ・検証方法）に従う。 実装消化は implement-issue、Issue 化は create-issue-tree（未導入なら create-issue）を参照。
fandhe-ai
planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.
am-will
event-budget
Build the budget and P&L for a technical event - every cost line split into fixed and per-head, the revenue mix against the funding model, a Good/Better/Best scope-tier ladder so break-even has three answers instead of one, a contingency sized as a stacked floor, pad and downgrade ladder, and outflows scheduled against the dates sponsor and ticket money actually lands. Use whenever asked to build an event budget, model conference or hackathon costs, find break-even, size a contingency reserve, plan event cash flow, or decide what to cut when revenue falls short. Consumes prices and real vendor quotes, never sets them. Do NOT use to set ticket or sponsor prices - use samber/dev-event-organizer-skills@event-ticket-pricing or samber/dev-event-organizer-skills@event-sponsor-pricing.
samber
memory-tasks
Task management via Basic Memory schemas: create, track, and resume structured tasks that survive context compaction. Uses BM's schema system for uniform notes queryable through the knowledge graph.
basicmachines-co
persona-project-manager
协调项目——跟踪任务、安排会议、共享文档。
googleworkspaceplanning-with-files-zht
基于 Manus 风格的文件规划系统，用于组织和追踪复杂任务的进度。建立 task_plan.md、findings.md 和 progress.md 三个文件。当用户要求规划、拆解或组织多步骤项目、研究任务或需要超过5次工具调用的工作时使用。支持 /clear 后的自动会话恢复。触发词：任务规划、项目计划、制定计划、分解任务、多步骤规划、进度追踪、文件规划、帮我规划、拆解项目
othmanadiplanning-with-files-es
基于文件的类Manus规划系统，用于组织和跟踪复杂任务的进度。创建 task_plan.md、findings.md 和 progress.md。当用户请求规划、分解或多步骤项目组织、研究任务或需要超过5次工具调用的工作时使用。支持 /clear 后的自动会话恢复。关键词：任务规划、项目规划、创建工作计划、分析任务、组织项目、进度跟踪、多步骤规划、帮我规划、分解项目
othmanadi
paperclip-converting-plans-to-tasks
Paperclip 将计划转化为可执行任务的方式。当你在 Paperclip 公司内被要求进行计划、范围界定或分解工作时使用。关于如何将计划转化为具有正确专业、依赖关系和并行化的已分配问题的行业无关指南，以便 Paperclip 的执行者能够接手工作——它不规定计划格式。与 `paperclip` 技能配合使用，该技能涵盖编写计划文档和重新分配问题的机制。
getpaperclipai
blueprint
Turn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief so a fresh agent can execute it cold. Includes adversarial review gate, dependency graph, parallel step detection, anti-pattern catalog, and plan mutation protocol. TRIGGER when: user requests a plan, blueprint, or roadmap for a complex multi-PR task, or describes work that needs multiple sessions. DO NOT TRIGGER when: task is completable in a single PR or fewer than 3 tool calls, or user says "just do it".
affaan-m
ralph-plan
Interactive planning assistant that helps create focused, well-structured ralph-loop commands through collaborative conversation
mastra-ai
blueprint
Map, analyze, and redesign the systems behind product experiences. Part of the Intent design strategy system. Creates service blueprints, ecosystem maps, process architecture, and dependency diagrams. Understands how services, teams, tools, and data flows connect to produce (or fail to produce) user outcomes. Proposes structural changes to how products and services are organized. Trigger on: service blueprints, system maps, process architecture, actor/role mapping, dependency analysis, cross-functional workflows, operational design, "how does this system work?", "what breaks when X happens?", "map out the service", "where are the dependencies?", or any question about the structural machinery behind a product experience. Use this skill broadly — whenever someone needs to understand or redesign how a system works, not just what a user sees.
ghaida
cron-schedule-planner
Builds an overview of GitHub Actions `schedule` cron expressions across multiple repositories and helps spread CPU-intensive jobs (Docker Compose, Testcontainers, Kind/k3s, matrix builds) into less contended slots. Use when the user asks 'when do my cron actions run?', 'do my scheduled builds collide?', 'when should the Testcontainers build run?', or wants a cron schedule overview/distribution report across repos. Scans via `gh` (no local checkouts required) or local checkouts, converts UTC to a local timezone, classifies job intensity, and writes a Markdown report with an hourly histogram, collisions and concrete cron redistribution suggestions.
dboeckli
research-planning
Design research plans and paper architectures. Given a research topic or idea, generate structured plans with methodology outlines, paper structure, dependency-ordered task lists, UML diagrams, and experiment designs. Use when starting a new research project or paper.
lingzhi227
planning-with-files
Uses persistent markdown files for general planning, progress tracking, and knowledge storage (Manus-style workflow). Use for multi-step tasks, research projects, or general organization WITHOUT mentioning PRD. For PRD-specific work, use prd-planner skill instead.
zhaono1
product-planner
Vision intake conversation followed by generation of three product documents — `docs/product-vision.md` (strategy and brand), `docs/prd.md` (technical spec for coding agents), and `docs/product-roadmap.md` (phased build plan with task checkboxes). Also captures the founder's answers as `docs/VISION.md`. Use when the founder says "plan my product", "plan a product", "define my vision", "generate a PRD", "create a roadmap", "spec out my idea", "help me build something", or wants to convert an idea into shippable spec documents.
buildgreatproducts
orchestrate-batch-refactor
Plan and execute large refactor or rewrite efforts efficiently with parallel multi-agent analysis and implementation. Use when a user asks to refactor many files, split workstreams, analyze a target code area, and coordinate sub-agents with clear ownership and dependency-aware execution.
dimillian