メニュー
Recognizing context pressure before it degrades output quality.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
Deep research with Analysis of Competing Hypotheses — use when asked to do deep research, deeply investigate, validate claims, or when correctness is critical and the user wants rigorous analysis with disconfirmation testing.
| name | context-budget |
| description | Recognizing context pressure before it degrades output quality. |
The context-monitor hook tracks usage tiers and injects warnings automatically. This skill covers what the hook can't detect — the subtle signs that quality is already degrading.
Watch for these before the hook's warnings fire:
If you notice these, treat it as POOR tier regardless of what the monitor says.
