pockerhead
- 4 skills
- 0 followers
- 11 hours ago last updated
- ▌ Maw Tasks · pockerheadCreate well-formed tasks for the MAW pipeline. Use when the user says "add a task", "create a task", "new task", or describes a feature/fix/refactor that should be tracked — even if they don't explicitly ask to create a task. Supports flag: --mode <full|small-fix|brainstorm|deep-research> to skip mode suggestion and set the mode directly.
- ▌ Maw Reason · pockerhead bundleExpensive, human-invoked adversarial deliberation over a QUESTION (not a task). Runs a five-role chain — premise check, generator, compressor, attacker, synthesizer — as real isolated spawns, and returns a synthesis with an explicit disagreement ledger and what-would-change-my-mind. Use when the cost of being wrong is high and genuine uncertainty exists: architecture forks, irreversible migrations, "should we X or Y" with real stakes. Do NOT use for lookups, trivia, or questions a single careful answer settles — it costs roughly 200-350k tokens and several minutes. Supports flags: --fast (lower compressor/attacker/synthesizer effort for speed, at the cost of a thinner attack surface), --keep (persist the trace for audit), --passes N (extra attack passes, default 1), --high-assurance (dual independent generators on distinct profiles, +1 spawn), --seed N (reproduce a previous run's role assignment), --force-premise (run the full chain even if the premise check flags the question). Model-invocation is guarded: i
- ▌ Maw Context · pockerheadAuthor and maintain the MAW project-context overlay (`maw/project-context/`) — the project knowledge the pipeline injects into agents. Use when the user says "add project context", "set up MAW for this project", "register a project invariant / rule / lesson / tool / skill / domain for the pipeline", or "review MAW context proposals". Supports flag: --review to go straight to folding pending PCTX_PROPOSALS.md entries.
- ▌ Maw Selfreview · pockerhead bundleOne-stage adversarial review of your own uncommitted diff, run by a different vendor than the one that wrote it. Use before committing work you produced in an ordinary session — no task folder, no pipeline, no branch handling. Costs one spawn and about a minute, against nine stages for the full pipeline. Reviews the diff only; it never edits code. Normally fires automatically from the pre-commit gate rather than being called by hand — the moment you would think to ask for it is the moment you are least likely to.