swingerman/discuss
engineer/skills/discuss/SKILL.md
Use when exploring a feature idea before committing, or revisiting a parked one. Triggers — "/engineer.discuss", "/engineer.discuss <slug>", "I have an idea about", "should we build", "let's think about".
$ install --global
skillsauthnpx skillsauth add swingerman/atdd 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: May 17, 2026, 4:28 AM328.9s1 file scanned
SKILL.md
- name:
- discuss
- description:
- Use when exploring a feature idea before committing, or revisiting a parked one. Triggers — "/engineer.discuss", "/engineer.discuss <slug>", "I have an idea about", "should we build", "let's think about".
discuss
The upstream funnel of DAE — a divergent brainstorm (forked from superpowers:brainstorming) that ends in one of three outcomes: drop, park, or promote. Most ideas die here; some park as features/NNN-slug/ with status: parked; survivors promote to status: ready.
When to use
- Fresh —
/engineer.discuss, no argument. New exploration. - Continue —
/engineer.discuss <slug>. Resume a parked feature.
Not for: feature-work prep on an already-Ready feature (prime-context), or editing a committed feature (feature-edit).
Workflow
- Resolve + load — resolve the methodology root + manifest via
${CLAUDE_PLUGIN_ROOT}/scripts/dae_resolve.py(seereferences/resolving.md). LoadCHARTER.mdand the last ~20 lines of.engineer/discussions.log. With a slug arg: also load that feature'sfeature.md+ priorhandoffs/*-discuss.md; reject if its status isready/in-progress(→feature-edit) ordone. - Open — fresh: "What are you thinking about?" After the first prompt, soft-match the topic against parked feature titles/areas; if a likely match, offer once to continue it. Continue mode: echo prior state in one line, then resume.
- Brainstorm (divergent) — explore intent, scope, alternatives; one question per turn. Surface charter signals (e.g. payment paths cap autonomy), ADR connections, and "too big — decompose?" flags as they arise.
- Surface the outcome — at a natural inflection, recommend an outcome (promote / park / drop); the user confirms. Never auto-execute. If the user says "drop" but there's a concrete reason it's worth parking, ask once.
- Execute the outcome:
- Drop — append one line to
.engineer/discussions.log:<ISO-timestamp> | <slug> | dropped | <one-line why>. Draft the "why" from context; user confirms/edits. - Park — invoke
feature-initwithfeature_intake { status: parked, autonomy_level: null, ... }. - Promote — first resolve
autonomy_level(low/medium/high, charter caps surfaced); if the user can't decide, fall back to park. Then invokefeature-initwithstatus: ready.
- Drop — append one line to
- Handoff — for park/promote, write a
<timestamp>-discuss.mdhandoff into the new feature folder. For drop, the log line is the record — no handoff.
Continuing a parked feature: each session appends a new discuss handoff; feature.md is refined in place. Promoting a continued feature flips status to ready directly — feature-init is not re-invoked.
Handoff
For park/promote, emit per ${CLAUDE_PLUGIN_ROOT}/references/handoff-summary.md. checkpoint: null. Drop emits no handoff.
References
- Discuss & Upstream Funnel — funnel, drop-log format, park/promote paths
- Foundation Design — feature.md schema, autonomy levels
- Sister skill:
feature-init(invoked for park/promote).
Related Skills
swingerman/post-merge
data-ai
VerifiedTrustedCommunity
Use immediately after a PR is merged to clean up the local feature branch and resync main. Triggers — "/engineer.post-merge", "did we merge", "did we push", "PR merged", "post-merge cleanup", or right after a `gh pr merge` succeeds in the same session.
103SKILL.mdUpdated Jun 5, 2026
swingerman/fix
data-ai
VerifiedTrustedCommunity
Use to drive a bug fix from first report through close, with a "why didn't we catch it?" loop at the end. Triggers — "/engineer.fix", "a bug came in", "this is broken", "a user reported X", "there's a defect", "we have a regression", "this needs a fix", "another report", "more issues", "still failing", "validation failed again", "another bug", "next defect", "more fixes".
103SKILL.mdUpdated May 26, 2026
swingerman/reorient
testing
VerifiedTrustedCommunity
Use mid-task when the working thread is lost — after a context compaction, a long agent run, or coming back to a feature unsure of the role, the current checkpoint, or the next action. Triggers — "/engineer.reorient", "reorient", "re-anchor", "what should I be doing right now", "I lost track", "where was I".
103SKILL.mdUpdated May 20, 2026
swingerman/arch-check
development
VerifiedTrustedCommunity
Use to check a feature's code against the charter's architecture rules — dependency layering, cycles, forbidden patterns, file naming, file size. Triggers — "/engineer.arch-check", "architecture check", "check architecture fitness", "does this follow the charter", "check layering".
103SKILL.mdUpdated May 19, 2026