@draht/coding-agent 2026.7.30 → 2026.9.5-1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +154 -0
- package/README.md +46 -2
- package/agents/debugger.md +12 -1
- package/agents/git-committer.md +1 -0
- package/agents/implementer.md +20 -0
- package/agents/investigator.md +75 -0
- package/agents/reviewer.md +7 -0
- package/agents/spec-reviewer.md +66 -0
- package/agents/verifier.md +4 -3
- package/bin/draht-tools.cjs +472 -41
- package/dist/agents/debugger.md +12 -1
- package/dist/agents/git-committer.md +1 -0
- package/dist/agents/implementer.md +20 -0
- package/dist/agents/investigator.md +75 -0
- package/dist/agents/reviewer.md +7 -0
- package/dist/agents/spec-reviewer.md +66 -0
- package/dist/agents/verifier.md +4 -3
- package/dist/cli/args.d.ts +10 -0
- package/dist/cli/args.d.ts.map +1 -1
- package/dist/cli/args.js +69 -2
- package/dist/cli/args.js.map +1 -1
- package/dist/cli/attach-mode.d.ts +61 -0
- package/dist/cli/attach-mode.d.ts.map +1 -1
- package/dist/cli/attach-mode.js +243 -5
- package/dist/cli/attach-mode.js.map +1 -1
- package/dist/cli/credential-print.d.ts +1 -1
- package/dist/cli/credential-print.d.ts.map +1 -1
- package/dist/cli/credential-print.js +5 -4
- package/dist/cli/credential-print.js.map +1 -1
- package/dist/config.d.ts +9 -0
- package/dist/config.d.ts.map +1 -1
- package/dist/config.js +31 -4
- package/dist/config.js.map +1 -1
- package/dist/core/agent-session-runtime.d.ts +17 -1
- package/dist/core/agent-session-runtime.d.ts.map +1 -1
- package/dist/core/agent-session-runtime.js +87 -30
- package/dist/core/agent-session-runtime.js.map +1 -1
- package/dist/core/agent-session-services.d.ts +1 -1
- package/dist/core/agent-session-services.d.ts.map +1 -1
- package/dist/core/agent-session-services.js +1 -0
- package/dist/core/agent-session-services.js.map +1 -1
- package/dist/core/agent-session.d.ts +35 -16
- package/dist/core/agent-session.d.ts.map +1 -1
- package/dist/core/agent-session.js +149 -64
- package/dist/core/agent-session.js.map +1 -1
- package/dist/core/auth-storage.d.ts +5 -1
- package/dist/core/auth-storage.d.ts.map +1 -1
- package/dist/core/auth-storage.js +72 -15
- package/dist/core/auth-storage.js.map +1 -1
- package/dist/core/builtins/checkpoints.d.ts +20 -0
- package/dist/core/builtins/checkpoints.d.ts.map +1 -0
- package/dist/core/builtins/checkpoints.js +161 -0
- package/dist/core/builtins/checkpoints.js.map +1 -0
- package/dist/core/builtins/duet.d.ts +26 -0
- package/dist/core/builtins/duet.d.ts.map +1 -0
- package/dist/core/builtins/duet.js +660 -0
- package/dist/core/builtins/duet.js.map +1 -0
- package/dist/core/builtins/index.d.ts.map +1 -1
- package/dist/core/builtins/index.js +7 -1
- package/dist/core/builtins/index.js.map +1 -1
- package/dist/core/builtins/subagent.d.ts +24 -4
- package/dist/core/builtins/subagent.d.ts.map +1 -1
- package/dist/core/builtins/subagent.js +278 -35
- package/dist/core/builtins/subagent.js.map +1 -1
- package/dist/core/checkpoints/checkpoint-cli.d.ts +17 -0
- package/dist/core/checkpoints/checkpoint-cli.d.ts.map +1 -0
- package/dist/core/checkpoints/checkpoint-cli.js +78 -0
- package/dist/core/checkpoints/checkpoint-cli.js.map +1 -0
- package/dist/core/checkpoints/checkpoint-manager.d.ts +294 -0
- package/dist/core/checkpoints/checkpoint-manager.d.ts.map +1 -0
- package/dist/core/checkpoints/checkpoint-manager.js +865 -0
- package/dist/core/checkpoints/checkpoint-manager.js.map +1 -0
- package/dist/core/checkpoints/rewind.d.ts +141 -0
- package/dist/core/checkpoints/rewind.d.ts.map +1 -0
- package/dist/core/checkpoints/rewind.js +246 -0
- package/dist/core/checkpoints/rewind.js.map +1 -0
- package/dist/core/compaction/branch-summarization.d.ts +1 -1
- package/dist/core/compaction/branch-summarization.d.ts.map +1 -1
- package/dist/core/compaction/branch-summarization.js +9 -4
- package/dist/core/compaction/branch-summarization.js.map +1 -1
- package/dist/core/compaction/compaction.d.ts +5 -0
- package/dist/core/compaction/compaction.d.ts.map +1 -1
- package/dist/core/compaction/compaction.js +25 -4
- package/dist/core/compaction/compaction.js.map +1 -1
- package/dist/core/extensions/index.d.ts +1 -1
- package/dist/core/extensions/index.d.ts.map +1 -1
- package/dist/core/extensions/index.js.map +1 -1
- package/dist/core/extensions/loader.d.ts.map +1 -1
- package/dist/core/extensions/loader.js +83 -20
- package/dist/core/extensions/loader.js.map +1 -1
- package/dist/core/extensions/runner.d.ts +13 -2
- package/dist/core/extensions/runner.d.ts.map +1 -1
- package/dist/core/extensions/runner.js +37 -2
- package/dist/core/extensions/runner.js.map +1 -1
- package/dist/core/extensions/types.d.ts +189 -6
- package/dist/core/extensions/types.d.ts.map +1 -1
- package/dist/core/extensions/types.js.map +1 -1
- package/dist/core/http-dispatcher.d.ts.map +1 -1
- package/dist/core/http-dispatcher.js +7 -0
- package/dist/core/http-dispatcher.js.map +1 -1
- package/dist/core/index.d.ts +1 -1
- package/dist/core/index.d.ts.map +1 -1
- package/dist/core/index.js.map +1 -1
- package/dist/core/keybindings.d.ts +5 -0
- package/dist/core/keybindings.d.ts.map +1 -1
- package/dist/core/keybindings.js +1 -0
- package/dist/core/keybindings.js.map +1 -1
- package/dist/core/model-registry.d.ts +3 -2
- package/dist/core/model-registry.d.ts.map +1 -1
- package/dist/core/model-registry.js +8 -8
- package/dist/core/model-registry.js.map +1 -1
- package/dist/core/model-resolver.d.ts.map +1 -1
- package/dist/core/model-resolver.js +34 -7
- package/dist/core/model-resolver.js.map +1 -1
- package/dist/core/model-runtime.d.ts +7 -1
- package/dist/core/model-runtime.d.ts.map +1 -1
- package/dist/core/model-runtime.js +30 -10
- package/dist/core/model-runtime.js.map +1 -1
- package/dist/core/multi-agent/permission-gate.d.ts.map +1 -1
- package/dist/core/multi-agent/permission-gate.js +4 -3
- package/dist/core/multi-agent/permission-gate.js.map +1 -1
- package/dist/core/multi-agent/worktree.d.ts +2 -0
- package/dist/core/multi-agent/worktree.d.ts.map +1 -1
- package/dist/core/multi-agent/worktree.js +2 -2
- package/dist/core/multi-agent/worktree.js.map +1 -1
- package/dist/core/package-manager.d.ts +7 -1
- package/dist/core/package-manager.d.ts.map +1 -1
- package/dist/core/package-manager.js +21 -44
- package/dist/core/package-manager.js.map +1 -1
- package/dist/core/permission-relay/index.d.ts +19 -0
- package/dist/core/permission-relay/index.d.ts.map +1 -0
- package/dist/core/permission-relay/index.js +49 -0
- package/dist/core/permission-relay/index.js.map +1 -0
- package/dist/core/permission-relay/relay-ui-context.d.ts +39 -0
- package/dist/core/permission-relay/relay-ui-context.d.ts.map +1 -0
- package/dist/core/permission-relay/relay-ui-context.js +788 -0
- package/dist/core/permission-relay/relay-ui-context.js.map +1 -0
- package/dist/core/permission-relay/types.d.ts +222 -0
- package/dist/core/permission-relay/types.d.ts.map +1 -0
- package/dist/core/permission-relay/types.js +15 -0
- package/dist/core/permission-relay/types.js.map +1 -0
- package/dist/core/pi-manifest.d.ts +14 -0
- package/dist/core/pi-manifest.d.ts.map +1 -0
- package/dist/core/pi-manifest.js +35 -0
- package/dist/core/pi-manifest.js.map +1 -0
- package/dist/core/project-trust.js +2 -2
- package/dist/core/project-trust.js.map +1 -1
- package/dist/core/resource-loader.d.ts +21 -0
- package/dist/core/resource-loader.d.ts.map +1 -1
- package/dist/core/resource-loader.js +101 -24
- package/dist/core/resource-loader.js.map +1 -1
- package/dist/core/sandbox/bash-operations.d.ts +149 -0
- package/dist/core/sandbox/bash-operations.d.ts.map +1 -0
- package/dist/core/sandbox/bash-operations.js +163 -0
- package/dist/core/sandbox/bash-operations.js.map +1 -0
- package/dist/core/sandbox/env.d.ts +83 -0
- package/dist/core/sandbox/env.d.ts.map +1 -0
- package/dist/core/sandbox/env.js +123 -0
- package/dist/core/sandbox/env.js.map +1 -0
- package/dist/core/sandbox/executor.d.ts +104 -0
- package/dist/core/sandbox/executor.d.ts.map +1 -0
- package/dist/core/sandbox/executor.js +92 -0
- package/dist/core/sandbox/executor.js.map +1 -0
- package/dist/core/sandbox/index.d.ts +36 -0
- package/dist/core/sandbox/index.d.ts.map +1 -0
- package/dist/core/sandbox/index.js +36 -0
- package/dist/core/sandbox/index.js.map +1 -0
- package/dist/core/sandbox/linux.d.ts +121 -0
- package/dist/core/sandbox/linux.d.ts.map +1 -0
- package/dist/core/sandbox/linux.js +260 -0
- package/dist/core/sandbox/linux.js.map +1 -0
- package/dist/core/sandbox/policy.d.ts +142 -0
- package/dist/core/sandbox/policy.d.ts.map +1 -0
- package/dist/core/sandbox/policy.js +297 -0
- package/dist/core/sandbox/policy.js.map +1 -0
- package/dist/core/sandbox/real-path.d.ts +112 -0
- package/dist/core/sandbox/real-path.d.ts.map +1 -0
- package/dist/core/sandbox/real-path.js +158 -0
- package/dist/core/sandbox/real-path.js.map +1 -0
- package/dist/core/sandbox/seatbelt-profile.d.ts +95 -0
- package/dist/core/sandbox/seatbelt-profile.d.ts.map +1 -0
- package/dist/core/sandbox/seatbelt-profile.js +239 -0
- package/dist/core/sandbox/seatbelt-profile.js.map +1 -0
- package/dist/core/sandbox/seatbelt.d.ts +95 -0
- package/dist/core/sandbox/seatbelt.d.ts.map +1 -0
- package/dist/core/sandbox/seatbelt.js +154 -0
- package/dist/core/sandbox/seatbelt.js.map +1 -0
- package/dist/core/sandbox/self-test.d.ts +109 -0
- package/dist/core/sandbox/self-test.d.ts.map +1 -0
- package/dist/core/sandbox/self-test.js +369 -0
- package/dist/core/sandbox/self-test.js.map +1 -0
- package/dist/core/sandbox/spawn.d.ts +33 -0
- package/dist/core/sandbox/spawn.d.ts.map +1 -0
- package/dist/core/sandbox/spawn.js +87 -0
- package/dist/core/sandbox/spawn.js.map +1 -0
- package/dist/core/sdk.d.ts.map +1 -1
- package/dist/core/sdk.js +3 -1
- package/dist/core/sdk.js.map +1 -1
- package/dist/core/session-manager.d.ts +60 -1
- package/dist/core/session-manager.d.ts.map +1 -1
- package/dist/core/session-manager.js +53 -6
- package/dist/core/session-manager.js.map +1 -1
- package/dist/core/settings-manager.d.ts +21 -0
- package/dist/core/settings-manager.d.ts.map +1 -1
- package/dist/core/settings-manager.js +36 -16
- package/dist/core/settings-manager.js.map +1 -1
- package/dist/core/skills.d.ts +3 -1
- package/dist/core/skills.d.ts.map +1 -1
- package/dist/core/skills.js +19 -6
- package/dist/core/skills.js.map +1 -1
- package/dist/core/slash-commands.d.ts.map +1 -1
- package/dist/core/slash-commands.js +1 -0
- package/dist/core/slash-commands.js.map +1 -1
- package/dist/core/soak/soak-log.d.ts +298 -0
- package/dist/core/soak/soak-log.d.ts.map +1 -0
- package/dist/core/soak/soak-log.js +660 -0
- package/dist/core/soak/soak-log.js.map +1 -0
- package/dist/core/soak/soak-reader.d.ts +60 -0
- package/dist/core/soak/soak-reader.d.ts.map +1 -0
- package/dist/core/soak/soak-reader.js +106 -0
- package/dist/core/soak/soak-reader.js.map +1 -0
- package/dist/core/socket-server/discovery.d.ts +78 -1
- package/dist/core/socket-server/discovery.d.ts.map +1 -1
- package/dist/core/socket-server/discovery.js +356 -37
- package/dist/core/socket-server/discovery.js.map +1 -1
- package/dist/core/socket-server/index.d.ts +10 -4
- package/dist/core/socket-server/index.d.ts.map +1 -1
- package/dist/core/socket-server/index.js +6 -3
- package/dist/core/socket-server/index.js.map +1 -1
- package/dist/core/socket-server/permission-delivery.d.ts +125 -0
- package/dist/core/socket-server/permission-delivery.d.ts.map +1 -0
- package/dist/core/socket-server/permission-delivery.js +152 -0
- package/dist/core/socket-server/permission-delivery.js.map +1 -0
- package/dist/core/socket-server/permission-registry.d.ts +301 -0
- package/dist/core/socket-server/permission-registry.d.ts.map +1 -0
- package/dist/core/socket-server/permission-registry.js +410 -0
- package/dist/core/socket-server/permission-registry.js.map +1 -0
- package/dist/core/socket-server/permission-relay.d.ts +81 -0
- package/dist/core/socket-server/permission-relay.d.ts.map +1 -0
- package/dist/core/socket-server/permission-relay.js +528 -0
- package/dist/core/socket-server/permission-relay.js.map +1 -0
- package/dist/core/socket-server/safe-text.d.ts +83 -0
- package/dist/core/socket-server/safe-text.d.ts.map +1 -0
- package/dist/core/socket-server/safe-text.js +277 -0
- package/dist/core/socket-server/safe-text.js.map +1 -0
- package/dist/core/socket-server/session-integration.d.ts +65 -2
- package/dist/core/socket-server/session-integration.d.ts.map +1 -1
- package/dist/core/socket-server/session-integration.js +434 -32
- package/dist/core/socket-server/session-integration.js.map +1 -1
- package/dist/core/socket-server/socket-client.d.ts +21 -2
- package/dist/core/socket-server/socket-client.d.ts.map +1 -1
- package/dist/core/socket-server/socket-client.js +52 -1
- package/dist/core/socket-server/socket-client.js.map +1 -1
- package/dist/core/socket-server/socket-server.d.ts +152 -1
- package/dist/core/socket-server/socket-server.d.ts.map +1 -1
- package/dist/core/socket-server/socket-server.js +775 -26
- package/dist/core/socket-server/socket-server.js.map +1 -1
- package/dist/core/socket-server/types.d.ts +106 -2
- package/dist/core/socket-server/types.d.ts.map +1 -1
- package/dist/core/socket-server/types.js +13 -1
- package/dist/core/socket-server/types.js.map +1 -1
- package/dist/core/system-prompt.d.ts.map +1 -1
- package/dist/core/system-prompt.js +8 -9
- package/dist/core/system-prompt.js.map +1 -1
- package/dist/core/tools/bash.d.ts +1 -1
- package/dist/core/tools/bash.d.ts.map +1 -1
- package/dist/core/tools/bash.js +5 -2
- package/dist/core/tools/bash.js.map +1 -1
- package/dist/core/tools/edit.d.ts.map +1 -1
- package/dist/core/tools/edit.js +17 -2
- package/dist/core/tools/edit.js.map +1 -1
- package/dist/core/tools/find.d.ts +3 -0
- package/dist/core/tools/find.d.ts.map +1 -1
- package/dist/core/tools/find.js +11 -18
- package/dist/core/tools/find.js.map +1 -1
- package/dist/core/trust-manager.d.ts +6 -4
- package/dist/core/trust-manager.d.ts.map +1 -1
- package/dist/core/trust-manager.js +55 -21
- package/dist/core/trust-manager.js.map +1 -1
- package/dist/extensions/index.d.ts.map +1 -1
- package/dist/extensions/index.js +5 -1
- package/dist/extensions/index.js.map +1 -1
- package/dist/extensions/llama/provider.d.ts.map +1 -1
- package/dist/extensions/llama/provider.js +5 -1
- package/dist/extensions/llama/provider.js.map +1 -1
- package/dist/extensions/stub-provider/index.d.ts +9 -0
- package/dist/extensions/stub-provider/index.d.ts.map +1 -0
- package/dist/extensions/stub-provider/index.js +13 -0
- package/dist/extensions/stub-provider/index.js.map +1 -0
- package/dist/extensions/stub-provider/provider.d.ts +77 -0
- package/dist/extensions/stub-provider/provider.d.ts.map +1 -0
- package/dist/extensions/stub-provider/provider.js +193 -0
- package/dist/extensions/stub-provider/provider.js.map +1 -0
- package/dist/hooks/gsd/draht-quality-gate.js +3 -3
- package/dist/index.d.ts +1 -1
- package/dist/index.d.ts.map +1 -1
- package/dist/index.js.map +1 -1
- package/dist/main.d.ts.map +1 -1
- package/dist/main.js +242 -45
- package/dist/main.js.map +1 -1
- package/dist/modes/interactive/components/config-selector.d.ts.map +1 -1
- package/dist/modes/interactive/components/config-selector.js +3 -2
- package/dist/modes/interactive/components/config-selector.js.map +1 -1
- package/dist/modes/interactive/components/extension-selector.d.ts +49 -0
- package/dist/modes/interactive/components/extension-selector.d.ts.map +1 -1
- package/dist/modes/interactive/components/extension-selector.js +202 -5
- package/dist/modes/interactive/components/extension-selector.js.map +1 -1
- package/dist/modes/interactive/components/session-selector.d.ts.map +1 -1
- package/dist/modes/interactive/components/session-selector.js +10 -2
- package/dist/modes/interactive/components/session-selector.js.map +1 -1
- package/dist/modes/interactive/components/settings-selector.d.ts +2 -0
- package/dist/modes/interactive/components/settings-selector.d.ts.map +1 -1
- package/dist/modes/interactive/components/settings-selector.js +10 -0
- package/dist/modes/interactive/components/settings-selector.js.map +1 -1
- package/dist/modes/interactive/components/tool-execution.d.ts.map +1 -1
- package/dist/modes/interactive/components/tool-execution.js +10 -1
- package/dist/modes/interactive/components/tool-execution.js.map +1 -1
- package/dist/modes/interactive/components/tree-selector.d.ts +20 -2
- package/dist/modes/interactive/components/tree-selector.d.ts.map +1 -1
- package/dist/modes/interactive/components/tree-selector.js +21 -5
- package/dist/modes/interactive/components/tree-selector.js.map +1 -1
- package/dist/modes/interactive/interactive-mode.d.ts +97 -3
- package/dist/modes/interactive/interactive-mode.d.ts.map +1 -1
- package/dist/modes/interactive/interactive-mode.js +394 -24
- package/dist/modes/interactive/interactive-mode.js.map +1 -1
- package/dist/modes/rpc/rpc-mode.d.ts.map +1 -1
- package/dist/modes/rpc/rpc-mode.js +165 -7
- package/dist/modes/rpc/rpc-mode.js.map +1 -1
- package/dist/modes/rpc/rpc-types.d.ts +68 -1
- package/dist/modes/rpc/rpc-types.d.ts.map +1 -1
- package/dist/modes/rpc/rpc-types.js.map +1 -1
- package/dist/prompts/commands/atomic-commit.md +1 -12
- package/dist/prompts/commands/brainstorm.md +12 -15
- package/dist/prompts/commands/create-verification-skill.md +108 -0
- package/dist/prompts/commands/discuss-phase.md +3 -14
- package/dist/prompts/commands/execute-phase.md +3 -11
- package/dist/prompts/commands/fix.md +41 -18
- package/dist/prompts/commands/grill.md +66 -0
- package/dist/prompts/commands/init-project.md +5 -15
- package/dist/prompts/commands/map-codebase.md +1 -13
- package/dist/prompts/commands/new-project.md +5 -15
- package/dist/prompts/commands/next-milestone.md +1 -13
- package/dist/prompts/commands/orchestrate.md +1 -1
- package/dist/prompts/commands/pause-work.md +1 -13
- package/dist/prompts/commands/plan-phase.md +2 -11
- package/dist/prompts/commands/progress.md +0 -13
- package/dist/prompts/commands/quick.md +3 -11
- package/dist/prompts/commands/resolve-conflicts.md +71 -0
- package/dist/prompts/commands/resume-work.md +0 -13
- package/dist/prompts/commands/review.md +4 -13
- package/dist/prompts/commands/triage.md +159 -0
- package/dist/prompts/commands/verify-work.md +4 -14
- package/dist/prompts/commands/why.md +135 -0
- package/dist/skills/atomic-reasoning/SKILL.md +115 -0
- package/dist/skills/blast-radius/SKILL.md +55 -0
- package/dist/skills/epistemics/SKILL.md +99 -0
- package/dist/skills/hexagon-animation/SKILL.md +49 -0
- package/dist/skills/hexagon-animation/generate.mjs +81 -0
- package/dist/skills/hexagon-animation/template.html +361 -0
- package/dist/skills/typescript-discipline/SKILL.md +50 -0
- package/dist/skills/typescript-discipline/references/patterns.md +294 -0
- package/dist/skills/unslop/SKILL.md +101 -0
- package/dist/utils/canonical-path.d.ts +28 -0
- package/dist/utils/canonical-path.d.ts.map +1 -0
- package/dist/utils/canonical-path.js +90 -0
- package/dist/utils/canonical-path.js.map +1 -0
- package/dist/utils/child-process.d.ts +12 -1
- package/dist/utils/child-process.d.ts.map +1 -1
- package/dist/utils/child-process.js +25 -8
- package/dist/utils/child-process.js.map +1 -1
- package/dist/utils/clipboard.d.ts +1 -1
- package/dist/utils/clipboard.d.ts.map +1 -1
- package/dist/utils/clipboard.js +22 -2
- package/dist/utils/clipboard.js.map +1 -1
- package/dist/utils/exif-orientation.d.ts.map +1 -1
- package/dist/utils/exif-orientation.js +2 -3
- package/dist/utils/exif-orientation.js.map +1 -1
- package/dist/utils/paths.d.ts +2 -7
- package/dist/utils/paths.d.ts.map +1 -1
- package/dist/utils/paths.js +13 -15
- package/dist/utils/paths.js.map +1 -1
- package/dist/utils/shell.d.ts.map +1 -1
- package/dist/utils/shell.js +6 -4
- package/dist/utils/shell.js.map +1 -1
- package/dist/utils/tools-manager.d.ts.map +1 -1
- package/dist/utils/tools-manager.js +3 -5
- package/dist/utils/tools-manager.js.map +1 -1
- package/docs/attachable-sessions.md +79 -0
- package/docs/compaction.md +21 -21
- package/docs/containerization.md +23 -23
- package/docs/custom-provider.md +16 -16
- package/docs/development.md +9 -9
- package/docs/docs.json +6 -2
- package/docs/duet.md +42 -0
- package/docs/extensions.md +58 -58
- package/docs/index.md +10 -10
- package/docs/json.md +7 -7
- package/docs/keybindings.md +6 -5
- package/docs/llama-cpp.md +6 -6
- package/docs/models.md +6 -6
- package/docs/packages.md +43 -43
- package/docs/prompt-templates.md +4 -4
- package/docs/providers.md +12 -12
- package/docs/quickstart.md +32 -32
- package/docs/rpc.md +83 -12
- package/docs/sdk.md +15 -15
- package/docs/security.md +18 -18
- package/docs/session-format.md +35 -13
- package/docs/sessions.md +17 -14
- package/docs/settings.md +25 -18
- package/docs/shell-aliases.md +2 -2
- package/docs/skills.md +12 -11
- package/docs/terminal-setup.md +12 -12
- package/docs/termux.md +6 -6
- package/docs/themes.md +11 -11
- package/docs/tmux.md +4 -4
- package/docs/tui.md +5 -5
- package/docs/usage.md +50 -50
- package/docs/windows.md +2 -2
- package/examples/extensions/overlay-qa-tests.ts +3 -3
- package/hooks/gsd/draht-quality-gate.js +3 -3
- package/package.json +11 -10
- package/prompts/commands/atomic-commit.md +1 -12
- package/prompts/commands/brainstorm.md +12 -15
- package/prompts/commands/create-verification-skill.md +108 -0
- package/prompts/commands/discuss-phase.md +3 -14
- package/prompts/commands/execute-phase.md +3 -11
- package/prompts/commands/fix.md +41 -18
- package/prompts/commands/grill.md +66 -0
- package/prompts/commands/init-project.md +5 -15
- package/prompts/commands/map-codebase.md +1 -13
- package/prompts/commands/new-project.md +5 -15
- package/prompts/commands/next-milestone.md +1 -13
- package/prompts/commands/orchestrate.md +1 -1
- package/prompts/commands/pause-work.md +1 -13
- package/prompts/commands/plan-phase.md +2 -11
- package/prompts/commands/progress.md +0 -13
- package/prompts/commands/quick.md +3 -11
- package/prompts/commands/resolve-conflicts.md +71 -0
- package/prompts/commands/resume-work.md +0 -13
- package/prompts/commands/review.md +4 -13
- package/prompts/commands/triage.md +159 -0
- package/prompts/commands/verify-work.md +4 -14
- package/prompts/commands/why.md +135 -0
- package/skills/atomic-reasoning/SKILL.md +115 -0
- package/skills/blast-radius/SKILL.md +55 -0
- package/skills/epistemics/SKILL.md +99 -0
- package/skills/hexagon-animation/SKILL.md +49 -0
- package/skills/hexagon-animation/generate.mjs +81 -0
- package/skills/hexagon-animation/template.html +361 -0
- package/skills/typescript-discipline/SKILL.md +50 -0
- package/skills/typescript-discipline/references/patterns.md +294 -0
- package/skills/unslop/SKILL.md +101 -0
- package/dist/prompts/agents/build.md +0 -86
- package/dist/prompts/agents/plan.md +0 -79
- package/dist/prompts/agents/verify.md +0 -69
- package/prompts/agents/build.md +0 -86
- package/prompts/agents/plan.md +0 -79
- package/prompts/agents/verify.md +0 -69
|
@@ -0,0 +1,135 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: "Investigate why code is the way it is — parallel evidence investigators, confidence-tiered cited synthesis"
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
# /why
|
|
6
|
+
|
|
7
|
+
Reconstruct why code is the way it is — the design rationale, the history, the rejected alternatives — from the evidence the repository and its surroundings actually carry. The output is a confidence-tiered, citation-backed answer with an explicit coverage map, never a plausible story.
|
|
8
|
+
|
|
9
|
+
## Usage
|
|
10
|
+
```
|
|
11
|
+
/why <file, symbol, or question>
|
|
12
|
+
```
|
|
13
|
+
|
|
14
|
+
Question: $ARGUMENTS
|
|
15
|
+
|
|
16
|
+
> **Tool note**: Use the `subagent` tool in **parallel mode** with the `investigator` agent — one task per available evidence category, dispatched in a single call. To escalate a contested synthesis, consult the `advisor` agent.
|
|
17
|
+
|
|
18
|
+
## Routing
|
|
19
|
+
|
|
20
|
+
`/why` answers intent, history, and forces. Something misbehaving right now is a defect — route it to `/fix`, which is reproduction-gated. A `/why` run that uncovers a live defect hands off to `/fix`; a `/fix` that needs design intent (is this behaviour a decision or an accident?) consults `/why`. For structure and architecture walkthroughs — what the code IS rather than why it is that way — use `/map-codebase`.
|
|
21
|
+
|
|
22
|
+
## Epistemics
|
|
23
|
+
|
|
24
|
+
Every claim in the output follows the `epistemics` skill — five confidence tiers, cite-or-label-as-inference, null results as evidence. Load it before synthesising; the epistemic framing is the product, and de-hedging it to sound authoritative is the exact failure this command exists to prevent.
|
|
25
|
+
|
|
26
|
+
## Steps
|
|
27
|
+
|
|
28
|
+
### 1 — Parse the target and the question archetype
|
|
29
|
+
|
|
30
|
+
Identify what is being asked about (file, symbol, pattern, value) and which archetype the question is: design rationale ("why is this a queue?"), tradeoff-vs-alternative ("why X instead of Y?"), defensive reasoning ("why the triple-check here?"), external forcing function ("why did this change in March?"), dead code ("why does this exist at all?"), or a broad sweep ("why is this module shaped like this?"). If the target is vague, state your best-guess interpretation from context and proceed — do not block on a clarifying question.
|
|
31
|
+
|
|
32
|
+
### 2 — Build the code anchor
|
|
33
|
+
|
|
34
|
+
Cheap, done once by the lead, pasted into every brief:
|
|
35
|
+
|
|
36
|
+
- file paths and line ranges; the key symbols involved
|
|
37
|
+
- `git blame -L <range> <file>` on the target lines
|
|
38
|
+
- `git log --follow --oneline -20 <file>`
|
|
39
|
+
- PR numbers extracted from `(#N)` commit subjects; for each, `gh pr view <n> --json title,body,author,createdAt,mergedAt,labels,closingIssuesReferences,comments,reviews`
|
|
40
|
+
- linked ticket and ADR identifiers found along the way
|
|
41
|
+
- optionally a pasted `draht-tools graph-context <file>` slice for orientation (lead-only; subagents cannot run draht-tools)
|
|
42
|
+
|
|
43
|
+
### 3 — Probe the evidence map
|
|
44
|
+
|
|
45
|
+
Five categories. Probe availability before dispatching; each row is the assigned investigator's playbook.
|
|
46
|
+
|
|
47
|
+
| Category | Availability probe | What it uniquely surfaces + playbook |
|
|
48
|
+
|---|---|---|
|
|
49
|
+
| Git history | Always available | Pickaxe (`git log -S`/`-G`), blame, `git show`; test names encoding edge cases; `red:`/`green:`/`refactor:` and `docs:` prefixes as semantic signal. Pitfalls: squash flatlands → fall back to the PR record; misleading messages → read the diff; cargo-culted patterns → investigate the origin commit; bot commits carry no motivation. |
|
|
50
|
+
| Review record | `git remote` + `gh auth status` | PR bodies, review threads, linked issues — the argument that happened before merge, including rejected alternatives. |
|
|
51
|
+
| Planning record | `.planning/` exists | `STATE.md` `## Decisions` (dated, attributed) and `## Lessons`; `phases/NN-*/` PLAN, SUMMARY, VERIFICATION, and UAT files (observed/derived/assumed labels); `specs/`; `quick/`; `loop/PROGRESS.md`; `CONTINUE-HERE.md`. Probe before assuming `.planning/decisions/` and `.planning/tickets/` — they exist only when a grill chose that output. |
|
|
52
|
+
| Decision records | `docs/adr/` and `CHANGELOG.md` files exist | ADR titles are decisions; dated Update blocks cite forcing commits; per-package changelogs date user-visible shifts. |
|
|
53
|
+
| External systems | A registered extension tool only | Tracker, chat, observability, error tracking, analytics — the conversational and operational record. Searchable only via a project-registered tool; when none exists, do not dispatch: record one Sources Consulted gap line — "External records: unavailable — no tool registered in this runtime; the conversational and operational record was not searched." |
|
|
54
|
+
|
|
55
|
+
The map is extensible: a project-registered tool adds an investigator with the same brief shape; an unavailable category is a coverage gap, never a silent drop.
|
|
56
|
+
|
|
57
|
+
**Incident overlay**: when the target looks defensive — null guards, retry, timeout, rate limiting, feature flags — instruct every investigator to hunt incident-shaped evidence inside its own category: revert-then-reapply chains, `## Lessons` entries, ADR Update blocks, UAT failure verdicts.
|
|
58
|
+
|
|
59
|
+
### 4 — Dispatch parallel investigators
|
|
60
|
+
|
|
61
|
+
Dispatch one `investigator` agent per AVAILABLE category in one parallel-mode call; follow the subagent tool limits (max 8 tasks, 4 concurrent) — if the category count ever exceeds them, fold overflow into the nearest category. Skip rules:
|
|
62
|
+
|
|
63
|
+
- A skip needs a written justification that surfaces in Sources Consulted. Unavailability is a gap, not a choice.
|
|
64
|
+
- "Provably irrelevant, not just probably" — a build-time script with no runtime path provably cannot appear in runtime error tracking; "it's feature code, error tracking won't have anything" is a guess, so search it.
|
|
65
|
+
|
|
66
|
+
Each brief is standalone:
|
|
67
|
+
|
|
68
|
+
```
|
|
69
|
+
You are investigating ONE evidence category for a why-question. Gather evidence, not narrative — a verbatim quote with a precise citation beats a paragraph of plausible summary.
|
|
70
|
+
|
|
71
|
+
Question: <the question and its archetype>
|
|
72
|
+
|
|
73
|
+
Code anchor:
|
|
74
|
+
<the anchor from Step 2>
|
|
75
|
+
|
|
76
|
+
Your category: <name + the playbook row from Step 3>
|
|
77
|
+
<if the incident overlay applies: hunt incident-shaped evidence inside your category — revert/re-apply chains, Lessons entries, ADR Update blocks, UAT failure verdicts>
|
|
78
|
+
|
|
79
|
+
Report using exactly these sections: Source / What I Searched (queries verbatim) / Direct Evidence Found / Indirect-Circumstantial Evidence (inference chain + alternative readings) / Contradictions / Gaps / Additional Leads.
|
|
80
|
+
|
|
81
|
+
Stay inside your category; record cross-category references under Additional Leads for the owning investigator — never chase them.
|
|
82
|
+
|
|
83
|
+
Do NOT run draht, draht-tools, or pi commands.
|
|
84
|
+
|
|
85
|
+
End with STATUS: DONE | DONE_WITH_CONCERNS | NEEDS_CONTEXT | BLOCKED
|
|
86
|
+
```
|
|
87
|
+
|
|
88
|
+
`NEEDS_CONTEXT` / `BLOCKED` → supply the missing info and re-dispatch. Hard cap: 3 re-dispatches total.
|
|
89
|
+
|
|
90
|
+
### 5 — Synthesize (the lead, in this context)
|
|
91
|
+
|
|
92
|
+
- Investigator claims are inputs, not verdicts — spot-verify load-bearing citations with git/gh before repeating them.
|
|
93
|
+
- Merge duplicate citations into one authoritative reference.
|
|
94
|
+
- Surface contradictions without picking a side.
|
|
95
|
+
- Tier every claim per the `epistemics` skill.
|
|
96
|
+
- Hand each investigator's Additional Leads to the owning category's follow-up, or record them as gaps.
|
|
97
|
+
- When competing hypotheses are decision-changing for an imminent code change, consult the `advisor` agent with the tiered findings for a steer.
|
|
98
|
+
|
|
99
|
+
### 6 — Output contract
|
|
100
|
+
|
|
101
|
+
Exact section order:
|
|
102
|
+
|
|
103
|
+
1. **The Question**
|
|
104
|
+
2. **The Code in Question** — what it does mechanically, in two or three sentences
|
|
105
|
+
3. **What We Found** — [Direct] and [Supported] bullets, each cited
|
|
106
|
+
4. **What We Can Reasonably Infer** — [Inferred] bullets with the chain visible: "Given A and B, C is likely because D"
|
|
107
|
+
5. **Competing Hypotheses** — hypothesis + evidence for + evidence against. Don't force a winner. Skip only when there is one clear answer.
|
|
108
|
+
6. **What We Don't Know** — specific searches that came up empty, named unavailable sources, people who would know
|
|
109
|
+
7. **Sources Consulted** — one line per category INCLUDING empties, gaps, and justified skips: `- <Category>: <what was searched>. <found / no relevant results / skipped: reason / unavailable: gap>`
|
|
110
|
+
8. **Confidence Summary** — 1-2 sentences
|
|
111
|
+
|
|
112
|
+
**Closing hook**: when the question precedes a change, convert the findings into a Preserve / Change / Avoid / Risk constraint set suitable for `/discuss-phase` or `/plan-phase`.
|
|
113
|
+
|
|
114
|
+
**Effort valve**: a trivial single-commit target whose PR or commit already answers the question may be handled inline by the lead running the git-history archaeology itself — only after stating why the other available categories would be redundant. The output contract and the coverage map still apply.
|
|
115
|
+
|
|
116
|
+
## Failure Modes — STOP
|
|
117
|
+
|
|
118
|
+
Stop immediately if you catch yourself:
|
|
119
|
+
|
|
120
|
+
- **Confident storytelling** — an uncited bullet belongs under Inferred or Hypotheses, never under What We Found
|
|
121
|
+
- Citing code as evidence of its own intent
|
|
122
|
+
- Recency bias — explaining an accretion as one decision; trace back
|
|
123
|
+
- Sycophantic agreement with the asker's embedded hypothesis
|
|
124
|
+
- Skipping the gaps section
|
|
125
|
+
- Skipping investigators by anticipation — a null result is a data point; a skipped search is a blind spot
|
|
126
|
+
- Collapsing categories into one investigator
|
|
127
|
+
|
|
128
|
+
## Rationalization Table
|
|
129
|
+
|
|
130
|
+
| Excuse | Reality |
|
|
131
|
+
|--------|---------|
|
|
132
|
+
| "The commit message says X, done" | One source is a lead, not a verdict — the record contradicts itself more often than it lies consistently. |
|
|
133
|
+
| "The code obviously does this for performance" | Code is mechanics; motivation needs an external source or an [Inferred] label. |
|
|
134
|
+
| "The user already told me why" | That is a hypothesis; check it independently. |
|
|
135
|
+
| "No .planning/ here, nothing to search" | git and gh still exist; report the missing categories as gaps, don't invent. |
|
|
@@ -0,0 +1,115 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: atomic-reasoning
|
|
3
|
+
description: Decompose work into atomic reasoning units before acting — state the logical component, validate independence, verify correctness. The discipline that opens every draht slash command. Use whenever planning, designing, refactoring, breaking down a feature, structuring a commit, or scoping work. Triggers on "plan", "decompose", "break down", "scope", "split", "atomic", "how should I structure", or any moment the agent is about to spawn many parallel changes without first carving the work into independently-verifiable units.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Atomic Reasoning
|
|
7
|
+
|
|
8
|
+
A meta-discipline. Before acting on any non-trivial piece of work, decompose it into atomic units — pieces that can be reasoned about, built, and verified independently.
|
|
9
|
+
|
|
10
|
+
This is the discipline that opens every draht slash command (`/plan-phase`, `/execute-phase`, `/fix`, `/quick`, `/verify-work`, `/atomic-commit`). The skill makes it explicit and available outside those commands too.
|
|
11
|
+
|
|
12
|
+
## The Three Questions
|
|
13
|
+
|
|
14
|
+
For each unit of work you're about to undertake, answer these three questions before doing anything else:
|
|
15
|
+
|
|
16
|
+
### 1. State the Logical Component
|
|
17
|
+
- What does this change do? What is its singular purpose?
|
|
18
|
+
- What observable outcome does it produce?
|
|
19
|
+
- Does it complete a thought, or is it half of one?
|
|
20
|
+
|
|
21
|
+
If you can't state the purpose in one sentence, the unit is not yet atomic — keep decomposing.
|
|
22
|
+
|
|
23
|
+
### 2. Validate Independence
|
|
24
|
+
- Can this be done without touching unrelated features?
|
|
25
|
+
- Does it depend on other units, or is it standalone?
|
|
26
|
+
- Which files does it touch? Are those files coupled to anything outside this unit's concern?
|
|
27
|
+
- If applied alone, would the codebase still build/run?
|
|
28
|
+
|
|
29
|
+
If the answer to "would it build alone" is *no*, the unit is too small — pair it with the dependency. If the answer to "does it touch unrelated concerns" is *yes*, the unit is too big — split it.
|
|
30
|
+
|
|
31
|
+
### 3. Verify Correctness
|
|
32
|
+
- What test or check would prove this unit works?
|
|
33
|
+
- What inputs → what expected outputs or state changes?
|
|
34
|
+
- What edge cases or failure modes exist?
|
|
35
|
+
|
|
36
|
+
If you can't name the proving test, you don't yet understand what "correct" means for this unit. Define it before building.
|
|
37
|
+
|
|
38
|
+
## How to Apply
|
|
39
|
+
|
|
40
|
+
### Before planning a feature
|
|
41
|
+
For each observable user-visible outcome:
|
|
42
|
+
1. State the logical component (what must be true for the user?)
|
|
43
|
+
2. Validate independence (which artifacts prove this? can it be built standalone?)
|
|
44
|
+
3. Verify correctness (what scenarios prove it works?)
|
|
45
|
+
|
|
46
|
+
### Validate a decomposition against the living map
|
|
47
|
+
Run `draht-tools graph-context <file...>` on each unit's files: a unit whose files share one cluster/bounded context is atomic; a unit spanning multiple contexts should be split along the boundary.
|
|
48
|
+
|
|
49
|
+
### Before splitting a commit
|
|
50
|
+
For each file in the diff:
|
|
51
|
+
1. State the logical component (what does this change accomplish?)
|
|
52
|
+
2. Validate independence (would this build alone? does it mix concerns?)
|
|
53
|
+
3. Verify correctness (is the change complete? does it leave a coherent intermediate state?)
|
|
54
|
+
|
|
55
|
+
### Before fixing a bug
|
|
56
|
+
1. State the logical component (what is the observed failure? what should happen vs what does?)
|
|
57
|
+
2. Validate independence (which components are involved? can we isolate it?)
|
|
58
|
+
3. Verify correctness (what test reproduces it reliably? what would prove it fixed?)
|
|
59
|
+
|
|
60
|
+
### Before refactoring
|
|
61
|
+
1. State the logical component (what structural change are you making?)
|
|
62
|
+
2. Validate independence (which behaviour-equivalence test proves this is a refactor, not a rewrite?)
|
|
63
|
+
3. Verify correctness (all tests stay green after the change?)
|
|
64
|
+
|
|
65
|
+
## Atomicity Heuristics
|
|
66
|
+
|
|
67
|
+
A unit is atomic if:
|
|
68
|
+
- ✅ It can be described in one sentence
|
|
69
|
+
- ✅ It can be built or applied in 2–5 minutes of focused work
|
|
70
|
+
- ✅ It can be verified by ONE test or check
|
|
71
|
+
- ✅ It touches ONE concern in the codebase
|
|
72
|
+
- ✅ All files in the atomic unit belong to one bounded context (or explicitly cross a documented boundary) — confirm with `draht-tools graph-context`
|
|
73
|
+
- ✅ It produces ONE commit (or one TDD red→green→refactor trio)
|
|
74
|
+
- ✅ Its `<files>` list contains specific paths, not "all relevant files"
|
|
75
|
+
- ✅ Its outcome is a concrete state change, not "improve X"
|
|
76
|
+
|
|
77
|
+
If any of these fail, decompose further.
|
|
78
|
+
|
|
79
|
+
## Order by Risk
|
|
80
|
+
|
|
81
|
+
Decomposition tells you the units; it doesn't tell you which to do first. When the units are independent, sequence is a lever — use it to fail cheaply.
|
|
82
|
+
|
|
83
|
+
Score each unit by **uncertainty** (has this codebase done it before?) × **blast radius** (how many other units become invalid if this one is wrong?). Do the highest-scoring unit first; push boilerplate last. Boilerplate never invalidates the plan — the risky, unfamiliar unit regularly does, and you want to discover that before you've built everything downstream of it.
|
|
84
|
+
|
|
85
|
+
*Example:* a feature needs a third-party webhook and a settings screen. Both are atomic. Prove the webhook round-trip first — if the contract isn't what you assumed, the settings screen you'd have built on top of it was wasted. *Prevents:* sinking effort into work that a later, riskier unit turns out to obsolete.
|
|
86
|
+
|
|
87
|
+
## Anti-Patterns — STOP
|
|
88
|
+
|
|
89
|
+
- **"Improve performance"** — not atomic. Pick one metric, one bottleneck, one change.
|
|
90
|
+
- **"Refactor the X module"** — not atomic. Pick one structural change with one behaviour-equivalence proof.
|
|
91
|
+
- **"Add error handling"** — not atomic. Pick one error case, one handler, one test.
|
|
92
|
+
- **"Wire up the Y feature"** — not atomic. Decompose into the components, the data flow, and the integration.
|
|
93
|
+
- **"And also fix the related bug while I'm there"** — that's a different atomic unit. Different commit.
|
|
94
|
+
|
|
95
|
+
## Relationship to TDD
|
|
96
|
+
|
|
97
|
+
Atomicity and TDD reinforce each other:
|
|
98
|
+
- TDD's RED phase forces you to name the proving test (Question 3) before building
|
|
99
|
+
- Atomic units fit naturally inside one RED → GREEN → REFACTOR cycle
|
|
100
|
+
- A test that requires changes in multiple unrelated files means the unit is not atomic
|
|
101
|
+
|
|
102
|
+
## Relationship to /atomic-commit
|
|
103
|
+
|
|
104
|
+
`/atomic-commit` is this skill applied to the git history: each commit is one atomic unit. The questions are the same; the artifact is a commit instead of a plan task.
|
|
105
|
+
|
|
106
|
+
## Relationship to subagent dispatch
|
|
107
|
+
|
|
108
|
+
Subagents work best on atomic units. When dispatching:
|
|
109
|
+
- Each subagent task should answer the three questions inside its prompt
|
|
110
|
+
- Parallel dispatch is only safe when units are genuinely independent (Question 2)
|
|
111
|
+
- A subagent returning `STATUS: BLOCKED — complexity` often means the unit wasn't atomic — split it.
|
|
112
|
+
|
|
113
|
+
## Output
|
|
114
|
+
|
|
115
|
+
This skill produces *thought*, not files. The artifact is a clearer plan / commit / fix scope before any code is written.
|
|
@@ -0,0 +1,55 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: blast-radius
|
|
3
|
+
description: Impact analysis beyond the diff — find what a change could break somewhere else before it ships, reduce the safety argument to the one falsifiable fact it rests on, and prove that fact by running real code, saying for every fact which rung of the evidence ladder it stopped at. Use for "what could this break", "blast radius of this change", or reviewing a small diff you don't trust yet. Not the uncertainty × blast-radius ordering heuristic in draht's planning commands — that phrase ranks risks for scheduling; this skill is the impact investigation itself.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Blast Radius
|
|
7
|
+
|
|
8
|
+
Find what a change breaks somewhere else, before it ships. Use for "what could this break", "blast radius of this change", or reviewing a small diff you don't trust yet.
|
|
9
|
+
|
|
10
|
+
Companion to `why`: `why` reconstructs why the code is shaped the way it is; blast radius works forward from a change to what it breaks elsewhere.
|
|
11
|
+
|
|
12
|
+
Listing the callers is not the job — grep finds those in a second. The job is the breakage grep won't show you.
|
|
13
|
+
|
|
14
|
+
## Don't Trust Your Own Writeup
|
|
15
|
+
|
|
16
|
+
A blast-radius writeup that sounds right is worthless. It reads as convincing whether or not it's true, and that is the trap. So don't hand back the writeup. Find the one or two facts the whole thing depends on and prove them by running code. Words are where you start, not what you ship.
|
|
17
|
+
|
|
18
|
+
## The Evidence Ladder
|
|
19
|
+
|
|
20
|
+
For each fact the change's safety depends on, get it as far down this ladder as is cheap, and **say where it stopped**:
|
|
21
|
+
|
|
22
|
+
1. **You said so.** Worthless on its own.
|
|
23
|
+
2. **You pointed at the line.** A real `file:line`, or the library's own source.
|
|
24
|
+
3. **You walked the failure.** You traced the bad case step by step and it doesn't reach.
|
|
25
|
+
4. **You ran it.** A script or test that calls the real code and fails loud if you're wrong.
|
|
26
|
+
5. **You reproduced it in the running app.**
|
|
27
|
+
|
|
28
|
+
Any safety fact you can't get to rung 4, say so out loud — don't write it up as settled. Rung 4 is usually one small script that imports the same library the app ships and calls the exact function you're worried about.
|
|
29
|
+
|
|
30
|
+
## Steps
|
|
31
|
+
|
|
32
|
+
1. **Read the change.** The diff, the symbols it adds, changes, and deletes, and what it now does differently — including the part the diff doesn't spell out. Pull the history behind it: `git log --follow` and `git log -S` on the touched files, `gh pr view` / `gh pr diff` for the PR that landed the code you're changing.
|
|
33
|
+
2. **Find the one fact it's safe because of.** Most changes that look scary are safe because of a single fact, like "this call only drops already-dead cache entries and does nothing else". Find that fact. If it holds, most of the scary cases die at once. Spend your time here, not on a long list of maybes.
|
|
34
|
+
3. **Look where grep stops.** Read the source of the library you call, at its pinned version, including any local patch. Work out when things run: microtasks, unmount and teardown, framework scheduling differences. Follow what a symbol search misses: the JSON an API returns, a DB column, a wire format, another language reading the same bytes, a feature flag, code three hops downstream.
|
|
35
|
+
4. **Be honest about each risk.** Give it a real chance of happening and a real cost if it does. Keep the risks you confirmed; list the ones you checked and cleared separately. Cite a real `file:line`; a search that finds nothing is still an answer; never invent a caller or an API.
|
|
36
|
+
5. **Prove the one fact.** Write a script or test that runs the real code, run it, and paste what happened. If you can't prove it cheaply, mark it unproven. Don't round up.
|
|
37
|
+
6. **For a big or wide change**, dispatch the `reviewer` and `security-auditor` subagents in parallel via `/review` and merge their findings with your own — different readers catch different real breakage.
|
|
38
|
+
|
|
39
|
+
## What to Hand Back
|
|
40
|
+
|
|
41
|
+
- **What it does.** What changed, including the part that isn't obvious.
|
|
42
|
+
- **The one fact it's safe because of.** State it, say which rung it reached, and show the proof. If you couldn't prove it, write unproven.
|
|
43
|
+
- **Risks.** Only the real ones. Each names how it breaks, the `file:line`, how likely and how bad, and how to check. Paste the proof for the ones that matter.
|
|
44
|
+
- **Cleared.** What you checked and why it's fine.
|
|
45
|
+
- **Before you merge.** The cheapest test or repro that catches the real bug, including the script you wrote.
|
|
46
|
+
|
|
47
|
+
Write it through `unslop`, cite real code, and strip anything private before it goes anywhere public.
|
|
48
|
+
|
|
49
|
+
**Reply:** the writeup above, with the one safety fact either proven or marked unproven.
|
|
50
|
+
|
|
51
|
+
## Relationship to Sibling Skills
|
|
52
|
+
|
|
53
|
+
- `verification-gate` demands evidence before claiming "done" or "safe" via the standard commands (tests, typecheck, lint). Rung 4 is that same iron rule applied to a single safety fact — a bespoke probe against the real code, because no standard command exercises the exact case you're worried about.
|
|
54
|
+
- `epistemics` calibrates claims about historical intent that nothing can run; blast radius governs claims about present breakage that something *can* run — so run it.
|
|
55
|
+
- draht-tools `graph-impact` walks the static import graph and is step-3's starting point, never its end: everything in "look where grep stops" is exactly what a static import walk cannot see.
|
|
@@ -0,0 +1,99 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: epistemics
|
|
3
|
+
description: Confidence calibration for investigation findings — five tiers (Direct, Supported, Inferred, Speculative, Unknown) that determine both which output section a claim goes in and how it is phrased; cite-or-label-as-inference; null results as first-class evidence; competing hypotheses without forcing a winner; the Sources Consulted coverage map. Use whenever reporting why code exists, summarising an investigation, writing a postmortem, or presenting findings whose evidence is historical, fragmentary, or secondhand. Triggers on "why was this built", "what's the history", "design rationale", "how confident are we", or any moment the agent is about to present an intent claim it cannot cite.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Epistemics
|
|
7
|
+
|
|
8
|
+
Code does not carry its own motivation. A diff shows what changed; nothing in it shows why. Every claim about intent, history, or rationale therefore rests on external evidence — a commit message, a PR description, a decision record, a planning note — and the honesty of a findings report lives in how precisely each claim's evidence is represented.
|
|
9
|
+
|
|
10
|
+
## The Core Rule
|
|
11
|
+
|
|
12
|
+
> **If you can't cite it, it's inference, not fact — and it must be labeled as such.**
|
|
13
|
+
|
|
14
|
+
A report that states inferences as facts is not a summary, it is fiction with a confident tone. The calibration below is the product; de-hedging it to sound authoritative is the exact failure this skill exists to prevent.
|
|
15
|
+
|
|
16
|
+
## The Five Tiers
|
|
17
|
+
|
|
18
|
+
The tier a claim earns determines **both** which output section it belongs in **and** the vocabulary allowed to phrase it.
|
|
19
|
+
|
|
20
|
+
1. **Direct** — an explicit statement of intent by someone in a position to know, citable verbatim. Phrase as fact with the citation adjacent.
|
|
21
|
+
- A PR description: "Switching to cursor pagination because offset scans time out past 100k rows" (PR #212).
|
|
22
|
+
- An ADR title and context section naming the decision and its forcing constraint.
|
|
23
|
+
- A `.planning/STATE.md` `## Decisions` line, dated and attributed.
|
|
24
|
+
2. **Supported** — multiple independent indirect sources converge on the same reading. Phrase as fact with all citations, and say the support is convergent, not explicit.
|
|
25
|
+
- A commit message names the symptom and the linked issue describes the incident it fixed.
|
|
26
|
+
- An inline comment names an upstream constraint and the dependency's changelog confirms it existed at that date.
|
|
27
|
+
3. **Inferred** — one plausible reading of circumstantial evidence. Phrase with hedged vocabulary and show the inference chain: "Given A and B, C is likely because D."
|
|
28
|
+
- The retry wrapper landed two days after a revert of the same call site — consistent with a reaction to a production failure, but nothing says so.
|
|
29
|
+
4. **Speculative** — a hypothesis the evidence neither supports nor rules out. Belongs only in a hypotheses section, phrased as a candidate, never in findings.
|
|
30
|
+
5. **Unknown** — the searches ran and came up empty, or the source that would know is unavailable. Reported explicitly, never silently omitted.
|
|
31
|
+
|
|
32
|
+
## Phrasing Guide
|
|
33
|
+
|
|
34
|
+
Confidence-carrying words assert knowledge of intent. Each one demands a citation immediately adjacent:
|
|
35
|
+
|
|
36
|
+
- "because", "the reason is", "was designed to", "fixes", "the team decided"
|
|
37
|
+
|
|
38
|
+
Hedge words mark inference and are the only vocabulary allowed for tier 3:
|
|
39
|
+
|
|
40
|
+
- "appears to", "likely", "suggests", "is consistent with", "one reading is"
|
|
41
|
+
|
|
42
|
+
Banned words: "obviously", "clearly", "of course", "just". And replace "I think" with "the evidence suggests" — the reader needs the evidence's confidence, not yours.
|
|
43
|
+
|
|
44
|
+
## Never Cite Code as Evidence of Its Own Intent
|
|
45
|
+
|
|
46
|
+
Code is mechanics; motivation is external. "The cache exists to reduce latency" cited to the cache implementation is circular — the code proves a cache exists, not why anyone wanted one. A performance rationale needs a source outside the code: a commit message, a benchmark in the PR, a decision record. Without one, it is an Inferred claim wearing a fact's clothes.
|
|
47
|
+
|
|
48
|
+
## Null Results Are Evidence; Skipped Searches Are Blind Spots
|
|
49
|
+
|
|
50
|
+
- A **null result** — "searched the review record for pagination discussion across the file's full history; nothing found" — is a data point. It rules readings out and belongs in the report.
|
|
51
|
+
- A **skipped search** is a blind spot. It rules nothing out and must be reported as a gap, not dressed up as a null result.
|
|
52
|
+
|
|
53
|
+
The reader cannot tell the two apart unless the report distinguishes them. Always state what was searched (queries verbatim) so an empty result is meaningful.
|
|
54
|
+
|
|
55
|
+
## Contradictions Are Findings
|
|
56
|
+
|
|
57
|
+
When two sources disagree — the commit message says performance, the linked ticket says a correctness bug — surface both with their citations. Do not pick the tidier narrative, do not average them into a vague middle. The historical record contradicts itself more often than it lies consistently, and the contradiction is usually the most informative thing the investigation found.
|
|
58
|
+
|
|
59
|
+
## The Sycophancy Trap
|
|
60
|
+
|
|
61
|
+
When the question embeds a hypothesis — "why did we switch to X, was it performance?" — the embedded guess is a candidate to check independently, not a conclusion to confirm. Search for evidence that would support it AND evidence that would contradict it, at equal effort.
|
|
62
|
+
|
|
63
|
+
> **The user's guess is a prompt for investigation, not a conclusion to validate.**
|
|
64
|
+
|
|
65
|
+
## Anti-Rationalization
|
|
66
|
+
|
|
67
|
+
- Never retrofit intent: "this must have been for scalability" is storytelling unless a source says so.
|
|
68
|
+
- A consistent pattern across files may be a deliberate convention — or copy-paste of the first instance. Investigate the origin, don't infer policy from repetition.
|
|
69
|
+
- Absence of evidence is not evidence of absence: "no discussion found" supports "we found no discussion", not "there was no discussion".
|
|
70
|
+
|
|
71
|
+
## The Coverage-Map Contract
|
|
72
|
+
|
|
73
|
+
Every findings report ends with a **Sources Consulted** map: one line per evidence category, including the empty ones. A category may be skipped only with a written justification, and only two justifications are valid:
|
|
74
|
+
|
|
75
|
+
1. **Unavailable in this runtime** — the source cannot be searched here. That is a coverage gap, not a choice, and is reported as one.
|
|
76
|
+
2. **Provably irrelevant, not probably.** A build-time script with no runtime path provably cannot appear in runtime error tracking. "It's feature code, error tracking won't have anything" is a probability judgment, not a proof — search it.
|
|
77
|
+
|
|
78
|
+
## Calibration Checklist
|
|
79
|
+
|
|
80
|
+
Before finalizing any findings report:
|
|
81
|
+
|
|
82
|
+
- Does every factual claim have a citation adjacent to it?
|
|
83
|
+
- Is every uncited claim phrased with tier-3 hedge vocabulary and filed in an inference section?
|
|
84
|
+
- Is any claim citing code as evidence of its own intent?
|
|
85
|
+
- Is the gaps section present and specific? **If no gaps are mentioned, that's suspicious** — every real investigation has them.
|
|
86
|
+
|
|
87
|
+
## Failure Modes
|
|
88
|
+
|
|
89
|
+
- **Confident storytelling** — a plausible narrative assembled from mechanics and phrased as history. The most common failure, and the hardest to spot from inside.
|
|
90
|
+
- **Citing code as evidence of its own intent** — circular sourcing dressed as citation.
|
|
91
|
+
- **Recency bias** — explaining the current shape as one decision when it is an accretion of many. Trace back through the history; the first version's rationale is usually not the current version's.
|
|
92
|
+
- **Sycophantic confirmation** — finding only the evidence that agrees with the asker's framing.
|
|
93
|
+
- **Skipping the gaps section** — shipping a coverage map with no empties is claiming a completeness no investigation has.
|
|
94
|
+
|
|
95
|
+
## Relationship to verification-gate
|
|
96
|
+
|
|
97
|
+
`verification-gate` governs claims about **present** state that a command can prove — run the command, read the output, then claim. Epistemics governs claims about **historical intent** that no command can prove: there is nothing to run, so the discipline is to tier and cite instead. The two compose; neither substitutes for the other.
|
|
98
|
+
|
|
99
|
+
One fixed-format carve-out: `verify-work`'s observed/derived/assumed labels and its verdict-first UAT ordering are fixed report formats — epistemics governs historical-intent claims and never rewords those labels or that ordering.
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: hexagon-animation
|
|
3
|
+
description: Generates a randomized 3D hexagon animation as a single self-contained HTML file - an isometric field of hexagonal prisms pulsing with seeded noise-driven waves, random palette, camera drift, and lighting. Use when the user asks for a hexagon animation, 3D hex grid, hex wave loop, generative background, or a similar abstract animation demo.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Hexagon Animation
|
|
7
|
+
|
|
8
|
+
Generates a self-contained HTML file (no dependencies, no network) that renders an
|
|
9
|
+
isometric field of 3D hexagonal prisms. Heights are driven by seeded 3D value noise
|
|
10
|
+
plus a traveling wave; palette, camera rotation, lighting, and motion parameters are
|
|
11
|
+
randomized per page load unless pinned.
|
|
12
|
+
|
|
13
|
+
## Usage
|
|
14
|
+
|
|
15
|
+
```bash
|
|
16
|
+
node generate.mjs # writes ./hexagon-animation.html, fully random
|
|
17
|
+
node generate.mjs --open # also opens it in the default browser
|
|
18
|
+
node generate.mjs --out demo.html # custom output path
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
Pin parameters for reproducible output:
|
|
22
|
+
|
|
23
|
+
```bash
|
|
24
|
+
node generate.mjs --seed 12345 --palette 3 --radius 10 --speed 1.5
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
| Option | Meaning |
|
|
28
|
+
|--------|---------|
|
|
29
|
+
| `--out <file>` | Output path (default `./hexagon-animation.html`) |
|
|
30
|
+
| `--seed <n>` | Pin the random seed; omit for a new look on every page load |
|
|
31
|
+
| `--palette <n>` | Palette index 0-7 (abyss, magma, acid, synth, royal, ember, mono, teal) |
|
|
32
|
+
| `--radius <n>` | Hex grid radius 3-16 (cell count grows quadratically) |
|
|
33
|
+
| `--speed <n>` | Motion speed multiplier |
|
|
34
|
+
| `--open` | Open the result in the default browser |
|
|
35
|
+
|
|
36
|
+
## In the browser
|
|
37
|
+
|
|
38
|
+
- `r` or click: new random seed
|
|
39
|
+
- `p`: cycle palette
|
|
40
|
+
- `space`: pause
|
|
41
|
+
- URL params `?seed=&palette=&radius=&speed=` override everything and are kept in
|
|
42
|
+
sync with the current state, so the URL is always shareable.
|
|
43
|
+
|
|
44
|
+
## Customizing
|
|
45
|
+
|
|
46
|
+
For variations beyond the flags (different palettes, bloom, taller prisms, more
|
|
47
|
+
octaves), copy `template.html` to the user's project and edit it directly - all
|
|
48
|
+
rendering lives in one inline script with the tunables grouped in `buildWorld()`
|
|
49
|
+
and the `PALETTES` array. Do not edit the template inside the skill directory.
|
|
@@ -0,0 +1,81 @@
|
|
|
1
|
+
#!/usr/bin/env node
|
|
2
|
+
// Generates a self-contained, randomized 3D hexagon animation HTML file from template.html.
|
|
3
|
+
// No dependencies. See SKILL.md for usage.
|
|
4
|
+
|
|
5
|
+
import { spawn } from "node:child_process";
|
|
6
|
+
import { readFileSync, writeFileSync } from "node:fs";
|
|
7
|
+
import { dirname, join, resolve } from "node:path";
|
|
8
|
+
import { fileURLToPath } from "node:url";
|
|
9
|
+
|
|
10
|
+
const args = process.argv.slice(2);
|
|
11
|
+
|
|
12
|
+
function usage(code) {
|
|
13
|
+
console.log(`Usage: node generate.mjs [options]
|
|
14
|
+
|
|
15
|
+
Options:
|
|
16
|
+
--out <file> Output HTML file (default: ./hexagon-animation.html)
|
|
17
|
+
--seed <n> Pin the random seed (default: random on every page load)
|
|
18
|
+
--palette <n> Pin the palette index 0-7 (default: derived from seed)
|
|
19
|
+
--radius <n> Hex grid radius, 3-16 (default: derived from seed)
|
|
20
|
+
--speed <n> Animation speed multiplier, e.g. 0.5 or 2 (default: derived from seed)
|
|
21
|
+
--open Open the generated file in the default browser
|
|
22
|
+
--help Show this help`);
|
|
23
|
+
process.exit(code);
|
|
24
|
+
}
|
|
25
|
+
|
|
26
|
+
const opts = { out: "hexagon-animation.html", open: false, config: {} };
|
|
27
|
+
const numericKeys = new Set(["seed", "palette", "radius", "speed"]);
|
|
28
|
+
|
|
29
|
+
for (let i = 0; i < args.length; i++) {
|
|
30
|
+
const arg = args[i];
|
|
31
|
+
if (arg === "--help" || arg === "-h") usage(0);
|
|
32
|
+
else if (arg === "--open") opts.open = true;
|
|
33
|
+
else if (arg === "--out") opts.out = args[++i];
|
|
34
|
+
else if (arg.startsWith("--") && numericKeys.has(arg.slice(2))) {
|
|
35
|
+
const key = arg.slice(2);
|
|
36
|
+
const value = Number(args[++i]);
|
|
37
|
+
if (!Number.isFinite(value)) {
|
|
38
|
+
console.error(`Invalid value for --${key}`);
|
|
39
|
+
process.exit(1);
|
|
40
|
+
}
|
|
41
|
+
opts.config[key] = value;
|
|
42
|
+
} else {
|
|
43
|
+
console.error(`Unknown option: ${arg}`);
|
|
44
|
+
usage(1);
|
|
45
|
+
}
|
|
46
|
+
}
|
|
47
|
+
|
|
48
|
+
if (!opts.out) {
|
|
49
|
+
console.error("Missing value for --out");
|
|
50
|
+
process.exit(1);
|
|
51
|
+
}
|
|
52
|
+
|
|
53
|
+
const templatePath = join(dirname(fileURLToPath(import.meta.url)), "template.html");
|
|
54
|
+
const template = readFileSync(templatePath, "utf-8");
|
|
55
|
+
|
|
56
|
+
const baked = Object.keys(opts.config).length > 0 ? JSON.stringify(opts.config) : "null";
|
|
57
|
+
const marker = /\/\*__CONFIG__\*\/[\s\S]*?\/\*__END_CONFIG__\*\//;
|
|
58
|
+
if (!marker.test(template)) {
|
|
59
|
+
console.error("template.html is missing the __CONFIG__ marker");
|
|
60
|
+
process.exit(1);
|
|
61
|
+
}
|
|
62
|
+
const html = template.replace(marker, `/*__CONFIG__*/ ${baked} /*__END_CONFIG__*/`);
|
|
63
|
+
|
|
64
|
+
const outPath = resolve(process.cwd(), opts.out);
|
|
65
|
+
writeFileSync(outPath, html);
|
|
66
|
+
console.log(`Wrote ${outPath}`);
|
|
67
|
+
if (Object.keys(opts.config).length > 0) {
|
|
68
|
+
console.log(`Pinned config: ${baked}`);
|
|
69
|
+
} else {
|
|
70
|
+
console.log("Fully random: every page load picks a new seed, palette, and motion parameters.");
|
|
71
|
+
}
|
|
72
|
+
|
|
73
|
+
if (opts.open) {
|
|
74
|
+
const [cmd, cmdArgs] =
|
|
75
|
+
process.platform === "darwin"
|
|
76
|
+
? ["open", [outPath]]
|
|
77
|
+
: process.platform === "win32"
|
|
78
|
+
? ["cmd", ["/c", "start", "", outPath]]
|
|
79
|
+
: ["xdg-open", [outPath]];
|
|
80
|
+
spawn(cmd, cmdArgs, { detached: true, stdio: "ignore" }).unref();
|
|
81
|
+
}
|