stevengonsalvez/discuss
toolkit/packages/skills/discuss/SKILL.md
Discuss and explore ideas before committing to an approach
$ install --global
skillsauthnpx skillsauth add stevengonsalvez/agents-in-a-box discussInstall 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 19, 2026, 2:33 AM8.3s1 file scanned
SKILL.md
- name:
- discuss
- description:
- Discuss and explore ideas before committing to an approach
- user-invocable:
- true
Discuss Phase
Capture implementation decisions BEFORE planning. Produces a CONTEXT.md with locked decisions that /plan must honor.
When to Use
- Before
/planwhen the phase has ambiguities - When starting a new phase in
.planning/ROADMAP.md - When the team needs to agree on approach before implementation
Process
Step 1: Load Phase Context
- Read
.planning/ROADMAP.mdto identify the target phase - Read
.planning/STATE.mdfor current position - If a phase number is provided as argument, use that
- If no argument, use current phase from STATE.md
Step 2: Identify Gray Areas
Based on what the phase is building, identify 3-4 ambiguities:
| Domain | Typical Gray Areas | |--------|-------------------| | UI/Frontend | Layout approach, interaction patterns, responsive behavior, state management | | API/Backend | Response formats, error handling, auth strategy, data validation | | Data/Storage | Schema design, migration approach, indexing strategy | | Infrastructure | Deployment target, scaling approach, monitoring |
Present them:
Phase [N]: [Name]
I've identified these areas that need decisions before planning:
1. **[Area 1]**: [Why this is ambiguous]
2. **[Area 2]**: [Why this is ambiguous]
3. **[Area 3]**: [Why this is ambiguous]
Which areas would you like to discuss? (or "all")
Step 3: Deep-Dive Questions
For each selected area, ask 3-4 probing questions using AskUserQuestion:
- Concrete choices (not abstract preferences)
- Trade-off acknowledgment
- Edge case handling
- Prior art / references
Step 4: Generate CONTEXT.md
Write to .planning/phases/{phase}/CONTEXT.md:
# Phase [N] Context: [Phase Name]
## Scope (from Roadmap)
[Copy from ROADMAP.md]
## Implementation Decisions
### [Area 1]
- **Decision**: [Concrete choice]
- **Rationale**: [Why this choice]
- **Trade-off**: [What we're giving up]
### [Area 2]
...
## Deferred Ideas
- [Idea mentioned but deferred to later phase]
---
*Locked on [date]. /plan must honor these decisions.*
Step 5: Update State
Update .planning/STATE.md to record that discussion is complete for this phase.
Without .planning/
If no .planning/ directory exists, /discuss still works:
- Ask what area/feature the user wants to discuss
- Run the same gray-area analysis and questioning
- Output to
plans/discuss_[topic]_[date].mdinstead
Related Skills
stevengonsalvez/reflect:cost
documentation
VerifiedTrustedCommunity
Report reflect drain spend over a time window — tokens split by cached (cache_read), uncached writes (cache_creation), and io (input+output), with a $ estimate, grouped by day / outcome / model / transcript. Reads the drainer's cost log and surfaces outlier runs and cache-reuse health (the 41.5M-token failure mode = low cache reuse + high cache writes). Use to answer "what is reflection costing me" for the last day / week.
12SKILL.mdUpdated Jun 2, 2026
stevengonsalvez/ainb-fleet:standup
development
VerifiedTrustedCommunity
Show fleet status — every claude session running on the host, merged across ainb + claude-peers broker + background jobs. Use when you need to enumerate sessions before composing an action, see which sessions have a peer registered (broker-routable) vs tmux-only, check the `summary` of each session, or pipe the list into jq for filtering. Default output: text table. Pass --format json for LLM consumption.
10SKILL.mdUpdated May 31, 2026
stevengonsalvez/ainb-fleet:sequence
testing
VerifiedTrustedCommunity
Ordered multi-step prompts to fleet targets, ack-gated between steps via JSONL assistant-turn-end detection. Use for cycles like disconnect→reconnect→verify, or any flow where step N+1 requires step N to have completed first. The skill BLOCKS until each target's transcript shows the next assistant turn finishing OR per-step timeout fires (default 300s).
10SKILL.mdUpdated May 31, 2026
stevengonsalvez/ainb-fleet:needs
development
VerifiedTrustedCommunity
Center control panel — enumerate every claude session that is blocked waiting on something: a user answer (AskUserQuestion fired), an API error retry, an idle assistant turn-end with no follow-up, or an explicit WAITING: marker. Returns rich JSON with signal kind + context per session. Use this when you've stepped away from the fleet and want one place to see everything that wants your attention and answer it.
10SKILL.mdUpdated May 31, 2026