本文へ移動
cccskills
無料GitHub で公開

codexkit-execution-planner

Turn ambiguous requests into an executable implementation plan with assumptions, sequence, acceptance checks, and rollback thinking.

インストール方法を見る

含まれるファイル(6)

  • SKILL.md2.2 KB
  • agents/openai.yaml228 B
  • examples/common-mistakes.md791 B
  • examples/good-output.md742 B
  • references/plan-template.md169 B
  • verification/checklist.md1.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Execution Planner

Use this skill when the request is larger than a quick patch and needs a plan that can survive real implementation.

Principles

  • keep the plan close to the code that will change
  • make assumptions explicit
  • sequence work to reduce rework
  • define how success will be checked

Workflow

  1. Restate the user goal in operational language.
  2. List constraints, dependencies, and assumptions.
  3. Break the work into thin, testable slices.
  4. Define acceptance checks for each slice.
  5. Note rollback or containment options for risky steps.

Output structure

Use the template in references/plan-template.md.

Avoid

  • task lists with no verification strategy
  • plans that front-load polish before foundations
  • broad estimates with no dependency reasoning

Quality Criteria

  • All placeholder sections are filled with domain-specific content
  • Structure follows the relevant industry standard or framework
  • Language matches target audience (technical / executive / legal)
  • Output is ready for review — not a rough draft requiring major rework

Verification (4C)

CheckQuestion
CorrectnessDoes the draft structure follow the stated framework or industry standard?
CompletenessAre all required sections present with substantive (not placeholder) content?
Context-fitDoes tone, detail level, and terminology match the intended audience?
ConsequenceIf sent to the intended recipient without further editing, what would fail?

Edge Cases

  • No existing template for this type — Use the closest available template and document all customizations made.
  • Stakeholder requirements conflict — Flag conflicts explicitly in the draft. Do not silently choose one requirement over another.
  • Output required in multiple formats — Produce the canonical format first, then derive others. Note any formatting limitations.

Changelog

  • v1.0.0 — Initial release

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月11日 更新

Review REST and GraphQL API designs for consistency, usability, and best practices. Covers naming conventions, versioning strategy, error format, pagination, authentication patterns, and breaking change detection. Use when reviewing API specs, designing new APIs, or auditing existing endpoints.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月11日 更新

Write Architecture Decision Records (ADRs) following the Michael Nygard format. Captures context, options considered, decision rationale, and consequences. Use when making technology choices, framework selections, or any architectural decision that future developers need to understand.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月11日 更新

Assess organizational readiness for financial audits (internal or external). Map assertions to account balances, check evidence completeness, score readiness using a Red/Amber/Green framework, and generate a remediation timeline. Aligned with SOX, IFRS, and GAAP audit standards. Use before scheduled audits or when preparing for first-time compliance.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月11日 更新

Design safe recurring Codex automations with clear prompts, outputs, schedules, and gating rules.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月11日 更新

Refine Product Backlog Items to meet INVEST criteria. Write User Stories with Acceptance Criteria in Given/When/Then format, estimate with Story Points, and flag dependencies. Use before sprint planning when backlog items need grooming. Do not use to prioritize the backlog — that is the Product Owner's decision.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月11日 更新

hoavdc のスキルをすべて見る

このスキルの問題を報告する