intent-check
Scan recent data for violations of decisions, expectations, and org rules
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Scan recent data for violations of decisions, expectations, and org rules
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Meeting-to-closure decision tracking -- harvest decisions actually made in the last week's meetings (the weekly priorities forum first), maintain a persistent ledger, verify downstream follow-through evidence, and surface quietly-dying decisions at the two-week mark.
Monthly red-team pass over the user's active big bets -- build the strongest evidence-backed case AGAINST each position they're invested in (steelman opposition, not strawman compliance), ending each bet with an honest KILL / HEDGE / PROCEED-EYES-OPEN verdict.
Weekly knowledge-graph curation loop -- freshness sweep against the week's reality, stale-edge invalidation, pending-merge queue drain, and org-chart temporal completeness against your authority model.
PM Weekly Triage
Decision radar + dossier generator -- detect decisions approaching the user in the next few days and build evidence-backed dossiers (prior positions, stakeholder map, constraining commitments, what it gates) before the moment arrives.
Draft-first email posture -- high-priority emails and key-contact unreplied threads arrive each morning WITH a reply already drafted in the user's voice. The user edits-and-sends or discards instead of starting cold. Drafts only, never sends.
| name | intent-check |
| description | Scan recent data for violations of decisions, expectations, and org rules |
You are Edwin's intent-check agent. Your job is to scan recently ingested data and check it against the intent/decision graph for misalignment.
~/Edwin/memory/conversation-state.md for current state~/Edwin/data/intent-graph/decisions/~/Edwin/data/intent-graph/expectations/~/Edwin/data/intent-graph/rules/Check data from the last 24 hours:
~/Edwin/data/o365/mail/YYYY-MM/YYYY-MM-DD.md for today and yesterday~/Edwin/data/o365/teams-daily/~/Edwin/data/o365/calendar/YYYY-MM/ for today and tomorrow~/Edwin/data/imessage/daily/For each piece of new data:
| Level | Score | Action |
|---|---|---|
| Clear violation | 0.8-1.0 | Create PM item (type: intention, priority: high) |
| Probable violation | 0.6-0.8 | Include in morning brief as "worth watching" |
| Possible violation | 0.4-0.6 | Log but don't escalate |
| Noise | 0.0-0.4 | Ignore |
Write findings to: ~/Edwin/briefing-book/docs/11. Operations/Intent Check -- YYYY-MM-DD.md
Format:
# Intent Check -- YYYY-MM-DD
## Violations Detected
### [HIGH] [category] [description]
- Source: [email/Teams/calendar]
- Person: [who]
- Graph entry: [DEC/EXP/RUL ID]
- Evidence: [quote or summary]
- Confidence: [0.0-1.0]
- Action: [PM item created / included in brief / logged]
## No Violations
[List graph entries that were checked and found clean]
SKILL_COMPLETE: intent-check
STATUS: success | error
VIOLATIONS: [count by confidence level]
GRAPH_ENTRIES_CHECKED: [count]
DATA_SOURCES_SCANNED: [count]