discuss

Explores feature ideas through structured brainstorming and routes them to drop, park, or promote outcomes.

150|10|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/swingerman/engineer --skill discuss-swingerman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discuss
Source: https://github.com/swingerman/engineer/tree/main/engineer/skills/discuss
Command: npx skills add https://github.com/swingerman/engineer --skill discuss-swingerman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Feature ideas often enter development pipelines without structured evaluation, leading to wasted effort on unvetted work. This Skill provides a disciplined upstream funnel that explores an idea through divergent brainstorming and ends in a clear decision: drop it, park it for later, or promote it to a ready feature. ## Core Features & Use Cases - Structured Brainstorming: Explores intent, scope, and alternatives one question at a time, surfacing charter signals, ADR connections, and decomposition flags. - Three-Way Outcome Routing: Ends every session with drop (logged to discussions.log), park (creates a parked feature via feature-init), or promote (creates a ready feature with an autonomy level). - Roadmap Integration: Soft-matches ideas against roadmap items, promotes planned items with back-links, and offers to add decomposed ideas as new roadmap entries. - Use Case: A developer says "I have an idea about adding payment retries." The Skill loads the project charter, brainstorms the idea, and either parks it as a feature folder or promotes it into the ATDD pipeline with a handoff. ## Quick Start Ask the assistant to run /engineer.discuss to explore a new feature idea, or /engineer.discuss <slug> to resume a parked one.

Frequently Asked Questions about discuss

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate a feature idea before committing to it?▼

Run /engineer.discuss with no argument to start a fresh exploration. The Skill brainstorms intent, scope, and alternatives one question per turn, then recommends dropping, parking, or promoting the idea based on the discussion.

How do I resume a parked feature idea?▼

Run /engineer.discuss followed by the feature slug. The Skill loads the parked feature's feature.md and prior discuss handoffs, echoes the prior state in one line, and continues the brainstorm from where it stopped.

What happens when an idea is promoted in the discuss workflow?▼

Promotion first resolves an autonomy level (low, medium, or high, capped by the project charter), then invokes the feature-init skill to create a ready-status feature. If the idea came from a roadmap item, its roadmap_ref is passed so the item is back-linked and marked in-progress.

When should I use the prototype path instead of promoting a feature?▼

Use the prototype path when the idea is fuzzy, UX-heavy, or better answered by building than talking. The discuss skill hands off to the prototype skill, which iterates a rough artifact and converts it to a spec later.

Can discuss edit a feature that is already in progress?▼

No. The Skill rejects features with ready or in-progress status and directs you to the feature-edit skill instead. It only handles fresh ideas and parked features.