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

exec-summary

Produce a short executive summary for the current rolling-wave project. Use when the user wants a concise status update, investor/team-friendly summary, leadership summary, project progress snapshot, or TL;DR of completed slices, the current slice plan, and upcoming slices.

rijkvanzanten/rolling-wave-engineering
インストール方法を見る

含まれるファイル（2）

  • SKILL.md3.0 KB
  • agents/openai.yaml255 B

SKILL.md（原文）

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

Exec Summary

Create a short executive summary of the current rolling-wave project.

Core Invariants

  • Work under docs/rolling-wave/{project}/.
  • Read project-level state from project.md; read slices from slices/NNN-slug.md.
  • Use slice statuses: pending, ready, in progress, ready for review, in review, done.
  • Treat the roadmap in project.md as the planned sequence.
  • This is read-only. Do not edit project or slice files.
  • Keep output concise and executive-friendly. Do not include planning-process caveats, file visibility notes, or test warnings unless directly relevant to the status.

Workflow

  1. Resolve the project.

    • If the user names a project, use docs/rolling-wave/{project}/.
    • If only one project exists under docs/rolling-wave/, use it.
    • If multiple projects exist and no project is named, ask which project to summarize.
    • If no rolling-wave project exists, say so plainly.

  2. Read status.

    • Read project.md.
    • Read slice files under slices/.
    • If a slice references a child rolling-wave project, read the child project.md only enough to summarize child status and current child slice.
    • Prefer slice file frontmatter for status when present.
    • Use the roadmap table in project.md for ordering and one-line purpose.

  3. Identify the current slice.

    • Prefer a slice with status in progress.
    • Else use in review.
    • Else use ready for review.
    • Else use ready.
    • Else use the first non-done roadmap slice.
    • If no unfinished slices remain, say the roadmap appears complete.

  4. Summarize.

    • Slices overview: use a markdown table with status and name columns in roadmap order.
      • Show each slice's exact status; do not reduce status to completed or incomplete.
      • For child-project-backed slices, append -> {child-project}: {child-status} or a similarly terse child-project marker to the name cell.
      • Include slice id/name and a short outcome- or purpose-oriented phrase in the name cell.
    • Current slice TL;DR: summarize the current slice plan in one to three bullets from its purpose, behavior, acceptance criteria, expected intermediate state, risks, and implementation notes.
    • Upcoming: include upcoming slices in the same table rather than a separate plain bullet list.
    • Include material project-level risks or review notes only if they affect leadership understanding of progress or next steps.

Output

Use this shape:

- Slices:
  
  | status | name |
  | --- | --- |
  | done | 001-...: ... |
  | in progress | 002-...: ... |
  | pending | 003-...: ... |
- Current slice:
  - ...

Keep the whole answer short. If there is nothing in a section, write none for that section.

レビュー

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

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

code-review

無料

Review local git changes before opening a PR or merging. First review all local tracked and untracked files; if none exist, review the current branch against a requested base branch or the Git Town parent branch. Use zero to three review subagents only when risk, diff size, language specificity, or uncertainty justifies the token cost, then report high-confidence bugs, regressions, risky assumptions, and missing tests. Use when the user asks for code review, local review, branch sanity check, pre-PR review, or review of work-in-progress changes.

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

rijkvanzanten/rolling-wave-engineering132026年8月18日 更新

code-simplify

無料

Review changed code for YAGNI, removable over-complexity, reuse, code quality, and efficiency, then apply worthwhile simplifications. Use when the user asks to simplify, clean up, tighten, de-hack recent changes, identify logic that can be dropped, or review whether added safeguards and edge-case handling are actually needed.

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

rijkvanzanten/rolling-wave-engineering132026年8月18日 更新

complete-slice

無料

Mark a rolling-wave slice done on explicit user authority, regardless of its current lifecycle status or missing implementation, finalization, review, verification, or child-project state. Use when the user says a slice is done, complete, finished, accepted, or should be marked done; capture available material learnings, update project state, and output roadmap progress without requiring earlier workflow steps.

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

rijkvanzanten/rolling-wave-engineering132026年8月18日 更新

debug

無料

Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says 'debug this', 'why is this failing', 'fix this bug', 'trace this error', or pastes stack traces, error messages, or issue references.

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

rijkvanzanten/rolling-wave-engineering132026年8月18日 更新

deliver-slice

無料

Implement and finalize one ready rolling-wave slice in one invocation while preserving the lifecycle boundary between implementation and independent review. Use when the user wants a slice delivered end to end without manually invoking implement-slice and finalize-slice, wants main-local implementation by default with workers only when delegation pays, followed by mandatory fresh-context finalization, or says deliver, implement and finalize, or take the slice through review.

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

rijkvanzanten/rolling-wave-engineering132026年8月18日 更新

finalize-slice

無料

Finalize an implemented rolling-wave slice for user review. Use when the user wants Codex to review the current branch state against a ready-for-review or in-review slice contract, confirm and fix required findings, repeat review and verification until no required findings remain, ask before accepting findings that materially change project shape or contradict project assumptions, record review state, and leave the clean slice in review for complete-slice.

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

rijkvanzanten/rolling-wave-engineering132026年8月18日 更新

rijkvanzanten のスキルをすべて見る

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