imabusyman/reasoning
prompts/squad/skills/reasoning/SKILL.md
Maintain the append-only reasoning log and write handoff envelopes for every squad delegation. Use this when the Conductor delegates to a specialist or when a specialist records a non-trivial decision.
testing
Updated Apr 25, 2026
$ install --global
skillsauthnpx skillsauth add imabusyman/CodebrewRouter reasoningInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 7:20 PM117.5s1 file scanned
SKILL.md
- name:
- reasoning
- description:
- Maintain the append-only reasoning log and write handoff envelopes for every squad delegation. Use this when the Conductor delegates to a specialist or when a specialist records a non-trivial decision.
Reasoning — squad decision log + handoff envelopes
This skill formalizes two disk artifacts that make squad runs auditable:
reasoning.log.md— append-only log of non-trivial decisions.handoff/NN-from-to-to.md— per-delegation envelope.
Follow the schemas exactly. Trivial edits (typo, method rename) do not belong in the log.
Reasoning log
Write one ##-level entry per decision. Schema (from prompts/squad/protocol/reasoning-log.schema.md):
## <ISO-8601 UTC> — <role> — <HIGH | MEDIUM | LOW>
Decision: <one factual sentence>
Rationale: <one or two sentences — why this, not something else>
Evidence: <artifact path, ADR number, PRD section, code line>
Log these (always)
- Every phase gate skipped or triggered (MEDIUM).
- Every
[ASK]relay and user answer (MEDIUM or HIGH). - Every architectural decision committed to an ADR draft (HIGH).
- Every deviation from
CLAUDE.md/ ADR defaults (HIGH). - Every mid-run file-lock change (HIGH).
Handoff envelope
One file per delegation at Docs/squad/runs/<run-id>/handoff/<NN>-<from>-to-<to>.md.
Schema from prompts/squad/protocol/handoff-envelope.schema.md:
---
from: <role>
to: <role>
phase: <integer>
task: <phase>.<task>
timestamp: <ISO-8601>
run_id: <run-id>
---
## Artifacts to re-read (required)
- <path>
## Files you may edit (exclusive lock, this phase)
- <path> (create | edit)
## Files other parallel tasks own (DO NOT TOUCH)
- <path>
## Inherited assumptions
- <decision>
## Pending decisions
- (none)
## Discarded context
- <option rejected earlier>
Validation:
- File-lock sets must be disjoint across parallel tasks in the same phase.
- Every "Artifacts to re-read" path must exist on disk.
- Paths are repo-relative with forward slashes.
Related Skills
imabusyman/write-a-prd
development
VerifiedTrustedCommunity
Generate a Product Requirements Document from a task description, user intent, or PRD outline. Structure the PRD with sections: Overview, Problem Statement, Goals, Scope, Features, Acceptance Criteria, Metrics. Use this when the Planner or Orchestrator needs to formalize requirements before decomposing into implementation steps.
SKILL.mdUpdated Apr 25, 2026
imabusyman/team-builder
development
VerifiedTrustedCommunity
Compose parallel teams of specialized agents for a multi-faceted task. Map subtasks to agent roles, balance workload, and validate team composition. Use this when breaking a task into parallel streams that require different expertise (Coder, Tester, Infra, etc.).
SKILL.mdUpdated Apr 25, 2026
imabusyman/subagent-driven-development
development
VerifiedTrustedCommunity
Delegate implementation work to specialized subagent instances, each inheriting a task scope and constraints from the parent. Emit structured handoffs, monitor completion signals, aggregate results. Use this in the Orchestrator parallel path when spawning independent Coder/Tester/Infra subagents from a single coordinator.
SKILL.mdUpdated Apr 25, 2026
imabusyman/quality-gate
development
VerifiedTrustedCommunity
Enforce the -warnaserror build + 95% coverage test gate on every squad [DONE]. Use this before any specialist (Coder, Tester, Reviewer, Infra) marks a phase complete.
SKILL.mdUpdated Apr 25, 2026