Rewrite crit into a concrete CRIT workflow #3

Closed
opened 2026-06-23 23:32:29 -04:00 by steve · 0 comments
Owner

Summary

common/pkm/crit/SKILL.md currently claims to use the CRIT framework, but the body is mostly generic assistant guidance. Replace it with a deterministic CRIT process.

Proposed workflow

Define each CRIT phase explicitly, for example:

  1. Context — restate problem, goal, constraints, and success criteria.
  2. Risks — identify assumptions, failure modes, tradeoffs, and blind spots.
  3. Ideas — generate divergent options.
  4. Test — choose the next experiment, decision, or artifact.

Acceptance criteria

  • CRIT is explicitly defined in the skill.
  • Each phase has a checkable completion criterion.
  • Generic no-op assistant guidance is removed.
  • The skill produces a predictable brainstorming/evaluation process.
## Summary `common/pkm/crit/SKILL.md` currently claims to use the CRIT framework, but the body is mostly generic assistant guidance. Replace it with a deterministic CRIT process. ## Proposed workflow Define each CRIT phase explicitly, for example: 1. Context — restate problem, goal, constraints, and success criteria. 2. Risks — identify assumptions, failure modes, tradeoffs, and blind spots. 3. Ideas — generate divergent options. 4. Test — choose the next experiment, decision, or artifact. ## Acceptance criteria - CRIT is explicitly defined in the skill. - Each phase has a checkable completion criterion. - Generic no-op assistant guidance is removed. - The skill produces a predictable brainstorming/evaluation process.
steve added a new dependency 2026-06-24 00:23:04 -04:00
steve closed this issue 2026-06-24 00:25:03 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: steve/skills#3