skills.rest
kamioj
kamiojCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-chat

Enable brainstorming discussions without altering documents in spec-driven development.

9|Updated May 27, 2026
Search Tags:#brainstorming#collaboration#spec-driven#software development#discussion mode
One-click install
npx skills add https://github.com/kamioj/spec-workflow --skill spec-chat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-chat
Source: https://github.com/kamioj/spec-workflow/tree/main/codex/skills/spec-chat
Command: npx skills add https://github.com/kamioj/spec-workflow --skill spec-chat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill allows for safe brainstorming and discussion in spec-driven development, without altering any documents or triggering document changes.

Core Features & Use Cases

  • Discussion Mode: Keeps all feedback as thinking material without touching documents.
  • Explicit State: Allows for clear distinction between brainstorming and actionable steps.
  • Mid-Flow Re-entry: Can switch to other stages like research, proposal, or design directly from chat mode.
  • Use Case: When reviewing a proposal, use spec-chat to discuss ideas without affecting the proposal or other documents.

Quick Start

Start a discussion about the proposal using the command: $spec-chat "We need to consider the user experience more deeply."

Frequently Asked Questions about spec-chat

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

FAQPage Schema
How do I brainstorm ideas during spec-driven development without altering existing documents?▼

Spec-driven brainstorming without document alteration is enabled by a dedicated discussion mode that keeps all feedback as thinking material, ensuring proposals and other files remain untouched during collaborative idea review.

Can I switch from a brainstorming discussion to actionable spec-driven stages mid-workflow?▼

Yes, mid-flow re-entry allows you to switch directly from the chat discussion mode to other actionable spec-driven stages like research, proposal, or design, facilitating a smooth transition from ideation to execution.

What is the best way to discuss a software development proposal collaboratively without triggering document changes?▼

The best way to discuss a proposal collaboratively without triggering document changes is using an explicit discussion state that separates brainstorming from actionable steps, keeping feedback isolated as thinking material.

Does spec-driven development require a special mode for safe collaborative decision-making?▼

Spec-driven development benefits from a special discussion mode for safe collaborative decision-making, as it prevents unintended document modifications while allowing iterative design processes to unfold through user interaction.

How do I start a discussion about user experience considerations in a spec-driven workflow?▼

You can start a discussion about user experience considerations by initiating a chat command with your topic, which opens the brainstorming mode for collaborative dialogue without affecting your current documents.

Related Skills

Explore More Software Engineering Skills→
rdkcentralrdkcentral

openspec-explore

Explore software development ideas with OpenSpec context and ASCII diagrams.

Official
Advanced
avav
3.2k

facts-refine

Refines draft facts into actionable specifications by resolving ambiguities, gaps, and contradictions.

Community
Intermediate
the-inconvenience-storethe-inconvenience-store
1

brainstorming

Guide structured brainstorming to create and validate software designs and specifications.

Community
Advanced
amadeus-dlcamadeus-dlc
5

amadeus-intent-capture

Run the ideation intent-capture stage in isolation with synthetic workflow reporting.

Official
Advanced