metawork

Draft or extend the canonical Meta Work methodology document by interview. Output is a PR-ready markdown section for the metawork-methodology repo.

Diagnose a Meta Work practice breakdown — escapist conflation, scope-axis mismatch, developmental-altitude pressure, panarchy-level confusion, fitness-function drift, polarity tilt, or practice-itself failure.

Run the four Living Forward daily perspective checks across your active Meta Work Groups.

Retrospect on Meta Work signals from this session or day — distinguish intentional Meta Work from escapist meta-work, surface open signals, recommend next moves.

Set up a new Meta Work Group — pick scope axes, name subject, walk the GTD Natural Planning Model, persist to your configured backend (OmniFocus or markdown).

Multi-Group operations for Meta Work — use when the user wants to set up Meta Work Groups for several projects in parallel, run morning checks across many groups concurrently, or perform a bulk operation (audit all active groups, find groups with drifted fitness functions, etc.). Parallelizable, read-and-write capable against backends.

Heavy Socratic teaching subagent for Meta Work. Use when a teaching arc would otherwise fill the main conversation context — e.g., a deep exploration of how polarity management interacts with vertical development stage, or a multi-pillar integration explanation. Grounded in references/methodology.md and references/pillars/*.md. Hands off to adjacent-practice skills rather than absorbing them. Read-only with respect to backends.

Use when the user (a practitioner) wants to draft or extend the canonical Meta Work methodology document. Interviews the user about a pillar, distinction, breakdown pattern, or integration point, then produces a PR-ready markdown section for the metawork-methodology repo (or, if cloning that repo isn't possible, a markdown file the user can copy in). Closes the loop with metawork-scholar — what articulate writes is what scholar teaches.

Use when the Meta Work practice is slipping — skipped reviews, drift from commitments, conflation of intentional Meta Work with escapist meta-work, polarities tilting hard to one pole, a Meta Work Group going stale. Diagnoses the breakdown using the methodology's own frameworks (scope-axis mismatch, developmental-altitude pressure, panarchy-level confusion, fitness-function drift, etc.) and routes to adjacent practices when the root cause sits outside Meta Work's lane.

Use as part of a morning practice — runs the four Living Forward daily perspective checks (acknowledge reality / aligned with purpose & principles / aligned with envisioned futures / aligned with goals & objectives) across the user's active Meta Work Groups. Records outcomes back to the backend. For OmniFocus users this maps to the daily auto-done perspective-check tasks in each Meta Work action group; for markdown users, appends to the group file with a dated entry.

Use at the end of a session or day to retrospect on Meta Work signals — what surfaced, what got scheduled, what got escapist (yak-shaved as work-about-work-as-avoidance), what got intentionally addressed. Routes to metawork-diagnose if a pattern of drift appears, or to lean-thinking-praxis if a structured root-cause analysis is warranted.

Use when the user wants to learn Meta Work as a methodology — its eight pillars (GTD Natural Planning Model, Living Forward, Polarity Management, Fitness Functions, Radical Acceptance, Panarchy & adaptive cycles, ADDRESSING, Vertical Development), how they integrate, common pitfalls, and the distinction between intentional Meta Work and escapist meta-work. Socratic style; grounds answers in references/methodology.md and references/pillars/. Hands off to adjacent practices (lean-thinking-praxis, daily-kaizen-audit, etc.) rather than absorbing them.