メニュー
Creates and maintains a live Notion tracking doc for audit runs. Standard format with overview table, live feed, per-domain sections, and findings summary. Used by qq-audit-master automatically.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Keep a live interactive chat session coming back to itself, visibly, after a usage/session cap interrupts it, never a silent background process. Invoke with /qq-cap-resume, or say “keep this session alive,” “resume yourself after the cap,” “don’t go dark on me,” any time a long interactive burn needs to survive a 5-hour session cap or ride out to a weekly reset without leaving you staring at a dead thread.
The unbounded end of the AFK spectrum: spend whatever it takes for quality, budget isn’t the constraint. Stand up a self-healing, fully-autonomous “kitchen-sink max-effort” campaign for a big multi-day initiative: resilience first, creative meta strategy, workflows spawning workflows, audit-gated quality, a phone-glanceable status surface with a proud wins list, and a long living tasklist. Invoke when you say “go HAM”, “go-ham”, “go afk ham”, “qq-go-afk-ham”, “kitchen sink”, “blow me away”, “use all the quota”, or hand it a large ambitious build to run autonomously for hours or days. For the frugal end, use `qq-go-afk-lean`; for the adaptive middle, use `qq-go-afk-smart`.
The adaptive middle of the AFK spectrum: picks the right model task by task, moment by moment, instead of committing to either extreme. Stand up a calm, self-healing, fully-autonomous overnight worker for a well-scoped punch list: the top-tier model writes strict specs and does quality control, cheap and free models do the grunt work, one bounded task per cycle, each one deployed and live-verified, a phone-glanceable status surface, and a durable done log. Invoke when you say “go afk smart”, “go-afk-smart”, “qq-go-afk-smart”, “go smart”, “bounded overnight”, “delegate and verify overnight”, or hand it a finite, well-specified backlog (a punch list, a rollout, a sweep) to grind down autonomously while you sleep, without the kitchen-sink fan-out of go HAM. For the unbounded end, use `qq-go-afk-ham`; for the frugal end, use `qq-go-afk-lean`.
The moment a real, avoidable mistake happens, name it plainly, root-cause the general class of it rather than just this one instance, and fix it at a level that prevents a repeat, not a note that gets written and forgotten. Then, before starting work that looks like it could repeat that shape, check the log first. A second occurrence of the same mistake means the note wasn’t enough, and it needs to become a real check instead of a reminder. Invoke with /ww-mistake-ledger, or say “log this mistake,” “close the loop on this,” “add this to the mistake log,” “check the mistake log first,” right after a preventable error, or right before starting work that resembles one already logged.
Ask what would make this fail before you build it, not after. A one-question design-time gate, imagine it’s already broken three months from now, work backward to the most likely cause, and let the answer change the plan instead of just getting noted and ignored. Works on code, an automation, a process, or a decision. Invoke with /ww-premortem, or say “what breaks this in three months,” “pre-mortem this,” “why would this fail,” “before I build this,” at the moment you’re about to commit to an approach, not after you’ve already started.
Before filling a gap in what you know with a guess, check whether the guess is load-bearing. If getting it wrong would mean redoing real work, or building on a false premise, ask a real question with concrete options instead of assuming silently. If it’s genuinely low-stakes, state the assumption out loud and keep moving rather than stalling on it. Works on any ambiguous request, with or without an AI agent involved. Invoke with /ww-questioning, or say “wait, let me ask first,” “is this load-bearing,” “check before I guess,” “clarify before building,” whenever a request has more than one reasonable reading and you’re about to just pick one.
| name | qq-audit-tracker |
| description | Creates and maintains a live Notion tracking doc for audit runs. Standard format with overview table, live feed, per-domain sections, and findings summary. Used by qq-audit-master automatically. |
| version | 1.0.0 |
| triggers | ["create audit tracker","audit tracking doc","audit notion doc"] |
Part of Claude Code operator skills: a collection of skills for running a real Claude Code setup.
Create and update a standard Notion tracking doc for live audit runs, recording progress per framework and fix.
Standard format for live audit tracking in Notion. Created at audit start, updated after every framework and fix. The user monitors this doc while agents work autonomously.
At the start of every audit run (invoked by qq-audit-master). Use your own Notion deliverables/tracking database. Set its data source ID in your project config rather than hardcoding one here.
Name: "Audit: [Product], [date]"
Project: [client name or your own org name]
Status: "Draft" → "Final" when complete
Session: [session name]
Notes: "[domain count] domains, [framework count] frameworks, target [N]/10"
Icon: 🔍
3-5 sentences. No jargon. What was audited, overall score, biggest problem, improvement from last audit. Updated after each domain completes.
<table fit-page-width="true" header-row="true">
<tr><td>Phase</td><td>Domain</td><td>Score</td><td>Target</td><td>Rounds</td><td>Status</td></tr>
<tr><td>UX</td><td>UX (N frameworks)</td><td>–</td><td>9.0</td><td>0/3</td><td>⏳ Pending</td></tr>
...
</table>
Status emoji: ⏳ pending, 🔄 in progress, ✅ score/10, ⚠️ hit max rounds, ⏭️ skipped
Running log of the spiciest findings as each framework and fix completes. Newest at top.
Entry format:
**HH:MM: [Event name]** ⬆️ old→new
One sentence: the finding or fix that matters most.
→ N fixes applied, N remaining
Rules:
One H1 toggle per domain. Inside each:
# UX domain {toggle="true"}
[Product]’s UX scored 8.8/10 across 20 frameworks. Biggest gap was consistency...
**Fixes:** 14 changes across 25 files
Populated after all domains converge:
The master orchestrator should:
notion-create-pages: initial creationnotion-update-page with update_content: all subsequent updatesnotion-fetch with include_discussions: true to check for the user’s comments