メニュー
Schedule software project work using priorities, estimates, dependencies, capacity, ownership, sprint plans, timelines, and delivery checkpoints. Use when organizing execution order and who does what when.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Design software system architecture using requirements, constraints, data models, APIs, integrations, dependencies, and technical tradeoff analysis. Use when deciding how a system or feature will fundamentally work.
Break software milestones, features, epics, requirements, and architecture plans into executable stories, tasks, and subtasks with clear boundaries and acceptance criteria.
Analyze software project dependencies, blockers, prerequisite work, critical paths, ownership constraints, external dependencies, and sequencing risks. Use when preventing execution deadlocks or delivery surprises.
Estimate software project effort, complexity, uncertainty, capacity, cost, and delivery ranges using scoped work, decomposed tasks, dependencies, and implementation risk.
Define measurable outcomes, KPIs, success criteria, acceptance thresholds, and decision criteria for software products, features, projects, or initiatives. Use when establishing what success looks like.
Generate and frame software product or feature ideas using user problems, market signals, constraints, and opportunity analysis. Use when brainstorming, discovering opportunities, or deciding what should exist and why it matters.
| name | scheduling |
| description | Schedule software project work using priorities, estimates, dependencies, capacity, ownership, sprint plans, timelines, and delivery checkpoints. Use when organizing execution order and who does what when. |
This skill helps turn prioritized and estimated software work into an execution schedule with owners, dates, sequencing, and checkpoints.
Use this skill when:
Expected inputs:
Inputs usually come from prioritization, estimation, and
dependency-analysis. If high-level sequencing is still unclear, use
roadmapping before scheduling execution.
Always optimize for:
Avoid optimizing solely for:
Determine:
Flag impossible combinations of scope, capacity, and date.
Order work by:
Schedule blockers and critical-path work early.
For each work item, define:
Avoid assigning ownerless work to a timeline.
Generate:
Avoid:
Before finalizing a schedule:
Escalate when:
Input:
Expected schedule:
Recommended next step:
goal-setting.