Template

Files

lmiranda 2d51df7a42 feat(marketplace): command consolidation + 8 new plugins (v8.1.0 → v9.0.0) [BREAKING]

Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action>
sub-command pattern. Git-flow consolidated from 8→5 commands (commit
variants absorbed into --push/--merge/--sync flags). Dispatch files,
name: frontmatter, and cross-reference updates for all plugins.

Phase 2: Design documents for 8 new plugins in docs/designs/.

Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate,
saas-react-platform, saas-test-pilot, data-seed, ops-release-manager,
ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents,
skills, README, and claude-md-integration. Marketplace grows from 12→20.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-06 14:52:11 -05:00

2.1 KiB

Raw Blame History

name

name
clarity clarify

/clarity clarify - Full Prompt Optimization

Visual Output

+----------------------------------------------------------------------+
|  CLARITY-ASSIST - Prompt Optimization                                |
+----------------------------------------------------------------------+

Purpose

Transform vague, incomplete, or ambiguous requests into clear, actionable specifications using the 4-D methodology with neurodivergent-friendly accommodations.

When to Use

Complex multi-step requests
Requirements with multiple possible interpretations
Tasks requiring significant context gathering
When user seems uncertain about what they want

Skills to Load

Load these skills before proceeding:

skills/4d-methodology.md - Core 4-phase process
skills/nd-accommodations.md - ND-friendly question patterns
skills/clarification-techniques.md - Anti-patterns and templates
skills/escalation-patterns.md - When to adjust approach

Workflow

Deconstruct - Break down request into components
Diagnose - Identify gaps and conflicts
Develop - Gather clarifications via structured questions
Deliver - Present refined specification
Offer RFC Creation - For feature work, offer to save as RFC

Output Format

Use the Deliver phase template from skills/4d-methodology.md to present the clarified specification for user confirmation.

RFC Creation Offer (Step 5)

After presenting the clarified specification, if the request appears to be a feature or enhancement:

---

Would you like to save this as an RFC for formal tracking?

An RFC (Request for Comments) provides:
- Structured documentation of the proposal
- Review workflow before implementation
- Integration with sprint planning

[1] Yes, create RFC from this specification
[2] No, proceed with implementation directly

If user selects [1]:

Pass clarified specification to /rfc-create
The Summary, Motivation, and Design sections will be populated from the clarified spec
User can then refine the RFC and submit for review

2.1 KiB Raw Blame History