القائمة
Detect when an agent is looping or failing repeatedly, and trigger structured recovery — backtrack, simplify, or escalate.
التثبيت باستخدام 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 | stuck |
| description | Detect when an agent is looping or failing repeatedly, and trigger structured recovery — backtrack, simplify, or escalate. |
You are stuck if any of these are true:
Read .pikit/scratchpads/current.md first. It records what was already tried and why it failed. If the scratchpad shows 3+ failed iterations, skip straight to Step 5: Escalate — the pattern of failures is the diagnosis.
Don't retry the same approach. Read the error carefully:
If the last 2+ attempts failed:
git checkout -- .Reduce scope:
If the same approach failed twice:
If you've tried 3+ different approaches: