skills.rest
MomoChenisMe
MomoChenisMeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

speclink-discuss

Initiate and record focused discussions as Markdown documents within Speclink.

1|Updated Jun 29, 2026
Search Tags:#CLI#knowledge capture#decision-making#discussion#Speclink
One-click install
npx skills add https://github.com/MomoChenisMe/speclink --skill speclink-discuss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speclink-discuss
Source: https://github.com/MomoChenisMe/speclink/tree/main/.agents/skills/speclink-discuss
Command: npx skills add https://github.com/MomoChenisMe/speclink --skill speclink-discuss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the need for organized, persistent discussions within the Speclink platform, facilitating structured decision-making and knowledge capture.

Core Features & Use Cases

  • Focused Discussion Mode: Enables targeted discussions with clear conclusions and decision trails.
  • Document Persistence: Discussions are saved as Markdown documents for future reference.
  • Workflow Integration: Seamlessly transitions from discussion to proposal creation or integration with existing workflows.
  • Use Case: Ideal for collaborative code reviews, feature discussions, and architectural decision-making within the Speclink ecosystem.

Quick Start

Start a discussion on the topic "Adding dark mode support" with the command: $speclink-discuss "Adding dark mode support"

Frequently Asked Questions about speclink-discuss

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

FAQPage Schema
How do I facilitate structured decision-making and knowledge capture for software architecture discussions?▼

Structured decision-making is facilitated by initiating focused discussions that produce clear conclusions and persistent Markdown documentation trails. This provides a framework for collaborative code reviews and architectural decisions.

Can I persist discussion records as Markdown documents for future reference within a CLI workflow?▼

Yes, discussion records are persisted as Markdown documents within the CLI workflow. This ensures all decision trails and knowledge capture outputs are saved for future reference and integration.

What is the best way to transition from a technical feature discussion to creating a formal proposal?▼

The best way to transition to proposal creation is by concluding the focused discussion mode within the Speclink ecosystem. This seamlessly integrates the documented decision trail into existing workflows.

Do I need CLI integration to record collaborative code review decisions?▼

Yes, CLI integration is required to record collaborative code review decisions. The framework utilizes the command line to initiate discussions and persist the resulting records as Markdown.

Are there limitations when using discussion mode for knowledge capture outside of the Speclink ecosystem?▼

Yes, a limitation is that the discussion mode is intended for use within the Speclink platform. Using it outside this ecosystem may break the workflow integration and proposal creation transitions.

Related Skills

Explore More Software Engineering Skills→
MomoChenisMeMomoChenisMe
1

speclink-apply

Automate task implementation in Speclink changes via the Speclink CLI.

Community
Advanced
roerohanroerohan
27

grill-with-docs

Validate implementation plans against project domain models and architectural decisions.

Community
Intermediate
WarLikeLauxWarLikeLaux
10

podcast

Generate a Markdown technical brief for a podcast episode on code review.

Community
Advanced
Avihai-HAvihai-H

azure-adr

Automate Azure Architecture Decision Records with WAF mapping, alternatives, and consequences.

Community
Advanced