メニュー
Executing implementation plans — work through steps methodically, verify each one, keep changes small and reviewable.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Recognizing context pressure before it degrades output quality.
Writing implementation plans — small testable steps, dependency ordering, upfront risk identification.
Evidence before claims, always — run verification commands and confirm output before making any completion or success claims.
Generate Architecture Decision Records — use when asked to document a decision, create an ADR, record why we chose X, or capture architectural rationale.
Generate a structured changelog from git history — use when asked to create a changelog, release notes, or summarize what changed between versions/tags/branches.
How to write pikit workflow YAML files — steps, loops, branches, interpolation.
| name | executing |
| description | Executing implementation plans — work through steps methodically, verify each one, keep changes small and reviewable. |
For each step in the plan:
Do not skip verify. Do not batch multiple steps into one change.
Commit after each verified step. Commit messages should reference the plan step:
step 3: add input validation to parseConfig
This creates a clean, reviewable history and makes it easy to bisect if something breaks later.
A step is done when: