deepwork-bar
Add, remove, or list written-bar criteria for the active deepwork session
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Add, remove, or list written-bar criteria for the active deepwork session
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Lightweight single-gate amendment for execute mode — spawns MICRO-TEAM (CRITIC + 1 specialist) for re-verdict without full deepwork re-run
View execute-mode session status — phase, plan_hash, drift, change_log, test results, 3-dimension verdict table, rollback log, discoveries
Run a deepwork session: research/design convergence (default) or plan execution (--mode execute). Design mode spawns a 5-archetype oppositional team and delivers an approved plan. Execute mode drives faithful implementation of an approved plan via role-asymmetric agents.
View deepwork session status — phase, team, bar verdicts, proposals, guardrails
End an active deepwork session — graceful per-teammate shutdown, archives state, and restores settings. CLI auto-cleans team dirs at session end. Works for both mid-flight abort and post-HALT cleanup.
Karpathy-style recap of deepwork history — reads DEEPWORK_WIKI.md Overview and the last 3 log entries, outputs 30-50 plain-text words
| name | deepwork-bar |
| description | Add, remove, or list written-bar criteria for the active deepwork session |
| argument-hint | add '<criterion>' [--categorical-ban] | remove <id> | list |
| allowed-tools | ["Read(${CLAUDE_PROJECT_DIR:-$(pwd -P)}/.claude/deepwork/**)","Write(${CLAUDE_PROJECT_DIR:-$(pwd -P)}/.claude/deepwork/**)","Edit(${CLAUDE_PROJECT_DIR:-$(pwd -P)}/.claude/deepwork/**)","Glob","Bash(jq:*)","Bash(mv:*)"] |
Manually manage the state.json.bar[] array — the gate criteria CRITIC verdicts against.
The args string passed to this skill is one of:
add "<criterion>" [--categorical-ban] — append a new criterion with auto-assigned id (G<N+1>). Use --categorical-ban for hard limits.remove <id> — remove the criterion with the given id (e.g., G3)list — show current bar criteria with verdictsGlob: ${CLAUDE_PROJECT_DIR:-$(pwd -P)}/.claude/deepwork/*/state.json
If no active session, report "No active deepwork session."
If multiple, AskUserQuestion to pick.
Parse the args string. Examples:
add "graceful rollback path exists"add "no new dependencies" --categorical-banremove G7listPerform the action:
add "<criterion>" [--categorical-ban]Compute next id (max existing + 1, starting at G1), then call the canonical writer:
STATE="${CLAUDE_PROJECT_DIR:-$(pwd -P)}/.claude/deepwork/<id>/state.json"
NEXT_ID=$(jq -r '
if (.bar // []) | length == 0 then "G1"
else
((.bar | map(.id | sub("^G"; "") | tonumber) | max) + 1) as $n
| "G\($n)"
end
' "$STATE")
bash "${CLAUDE_PLUGIN_ROOT}/scripts/state-transition.sh" \
--state-file "$STATE" bar_add \
--id "$NEXT_ID" \
--statement "<criterion>" \
$( [[ "<categorical-ban-flag>" == "--categorical-ban" ]] && echo "--categorical-ban" )
Report: "Added bar criterion : . CRITIC will verdict against this on the next CRITIQUE cycle."
remove <id>Delete the entry with matching id via the canonical writer:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/state-transition.sh" \
--state-file "$STATE" bar_remove --id "<id>"
Report the removed criterion, or error if not found.
Warning: if the bar is currently CRITIQUE-active and the removed criterion had a PASS verdict, the removal is fine. If it had FAIL/CONDITIONAL, the orchestrator should not take this as "problem solved" — ask the user to confirm.
listPrint:
Bar for instance <id>:
G1 [PASS] functional goal achieved
evidence: proposals/v2.md:45 cites X
G2 [HOLDING] preserves REPL interactivity
evidence: coverage.terminal.md matrix
G3 [CATEGORICAL BAN] no minified-JS line pinning without feature-detect
(no verdict yet — applied at CRITIQUE)
...
Show [CATEGORICAL BAN] flag next to criteria with categorical_ban: true. Show [<verdict>] if verdict is set, else [pending].
If empty: "Bar not yet populated. Orchestrator will populate in SCOPE phase."