ワンクリックでManusで任意のスキルを実行

planning-and-task-breakdown

スター6

フォーク1

更新日2026年7月22日 13:29

Task ledger: Use when ready decisions need one delegated, dependency-ordered tasks.md with owners, proof, cleanup, and reopen conditions. Own faithful ledger authoring; Skip when behavior remains unresolved, implementation is requested, or root planning-phase ownership and readiness review are needed.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

Dankosik

Dankosik/go-service-template-rest

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Planning And Task Breakdown

Must read Planning; it owns the ledger shape and readiness boundary. Build the smallest candidate ledger from implementation-changing accepted obligations. Give each task an owner, real dependencies, matching proof, and cleanup or reopen condition only when present. Do not create waves for sequential work. Authoring ends when the next task or real parallel wave can execute without inventing policy; escalate only blockers that can invalidate that work.

このリポジトリの他の Skills

同じリポジトリ

go-systematic-debugging

Dankosik/go-service-template-rest

Root cause: Use when a Go bug, flaky test, build failure, hang, deadlock, timeout incident, or production regression needs causal diagnosis. Own the first broken invariant and, only when authorized, the smallest causal fix and replayed proof; Skip when feature implementation, unresolved policy design, broad review, or claim-only verification is primary.

2026-07-266

pre-spec-challenge

Dankosik/go-service-template-rest

Pressure-test: Use when existing research or framing needs a few independent, discriminating questions before specification or planning. Own hidden assumptions, ownership, failure semantics, irreversible consequences, and rollout risk, plus the next owner; Skip when framing is blank, ordinary spec review is needed, or one isolated high-impact approval question is primary.

2026-07-266

spec-clarification-challenge

Dankosik/go-service-template-rest

Approval question: Use when one candidate-spec decision is high-impact, hard to reverse, or explicitly challenged. Own a read-only pressure test with evidence, options, a recommended option, and decision owner; Skip when framing is blank, whole-spec review is needed, or the clarification is low-impact.

2026-07-266

spec-first-brainstorming

Dankosik/go-service-template-rest

Problem frame: Use when a chosen or mostly chosen feature/refactor direction still needs an engineering-ready behavior delta, scope, constraints, assumptions, and readiness decision. Own that frame, its decided defaults, surviving user-owned questions, challenge routing, and next owner; Skip when raw ideation, final design decisions, or task breakdown is primary.

2026-07-266

go-delivery-platform

Dankosik/go-service-template-rest

Delivery platform: Use when CI/CD gates, release trust, drift controls, containers, migrations, or rollout policy needs a decision, or when changed delivery controls need conformance review. Own delivery acceptance and review; Skip when API, data, security, reliability, or pipeline implementation is primary.

2026-07-256

go-test-strategy

Dankosik/go-service-template-rest

Test strategy: Use when accepted behavior needs risk scenarios, proof levels, deterministic oracles, or executable gates, or when changed tests and validation evidence need review. Own proof design and test conformance; Skip when behavior is unresolved, tests must be implemented, or completion claims need validation.

2026-07-256

ワンクリックで任意のスキルを実行

name	planning-and-task-breakdown
description	Task ledger: Use when ready decisions need one delegated, dependency-ordered tasks.md with owners, proof, cleanup, and reopen conditions. Own faithful ledger authoring; Skip when behavior remains unresolved, implementation is requested, or root planning-phase ownership and readiness review are needed.