planning-session

Sterne6

Forks1

Aktualisiert22. Juli 2026 um 13:29

Ledger readiness: Use when the full root planning phase must complete through tasks.md authoring or repair, task review, findings repair, and its stop rule. Own phase orchestration and accepted planning readiness; Skip when only delegated draft breakdown or implementation is requested.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

Dankosik

Dankosik/go-service-template-rest

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	planning-session
description	Ledger readiness: Use when the full root planning phase must complete through tasks.md authoring or repair, task review, findings repair, and its stop rule. Own phase orchestration and accepted planning readiness; Skip when only delegated draft breakdown or implementation is requested.

Planning Session

Must read Planning; it owns ledger authoring, readiness, and the implementation-start boundary. Produce the smallest owned ledger whose next task or real parallel wave is executable and provable. Apply root self-review; use independent Readiness Review only when its shared trigger applies. Carry dispositioned later concerns forward, and seek fresh review only after FAIL repair or material candidate change. Stop when Planning permits implementation or names the owner to reopen.

Mehr aus diesem Repository

gleiches Repository

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

Jeden Skill mit einem Klick ausführen