πŸ”Œ

spec

πŸ”ŒPlugin

pandysp/claude-plugins

VibeIndex|
What it does
|

Write the implementation spec (context, approach, files to modify, utilities to reuse, and verification) that drives execution after design is chosen.

πŸͺ

Part of

pandysp/claude-plugins

workflowspecimplementation-planscopedesignpre-execution

Installation

Add marketplace in Claude Code:
/plugin marketplace add pandysp/claude-plugins
Step 2. Install plugin:
/plugin install spec@pandysp
0
-
AddedJul 14, 2026

More from this repository10

πŸ”Œ
worktrunk-hookπŸ”ŒPlugin

Route Claude Code's auto-created git worktrees through worktrunk so background and --worktree sessions inherit project hooks (env symlinks, installs, port allocation).

πŸ”Œ
reflectπŸ”ŒPlugin

Capture durable lessons from a session before they fade: what surprised you, what friction repeated, what should update CLAUDE.md or notes. Output goes to memory, notes, or global instructions, not just to chat.

πŸ”Œ
clarifyπŸ”ŒPlugin

Surface and resolve underspecified decisions before designing. Asks targeted questions about scope, edge behavior, trade-offs, integration, constraints, and audience (with defaults), so design choices aren't silently locked around hidden assumptions.

πŸ”Œ
quality-reviewπŸ”ŒPlugin

Multi-lens quality audit for docs, code, and other artifacts. 13 quality adjectives as audit lenses with per-domain translation sheets, a workflow-backed finder/verifier pipeline, and lens-yield reporting.

πŸ”Œ
pre-mortemπŸ”ŒPlugin

Systematically identify how a plan or design could fail before committing to it.

πŸ”Œ
understudyπŸ”ŒPlugin

Write code, comments, tests, or commit messages that read as if the project's own maintainer wrote them, so a contribution is accepted as native rather than rejected as foreign. A foreign-looking patch is a cost to the maintainer even when it's correct.

πŸ”Œ
silent-failuresπŸ”ŒPlugin

Audit error handling for silent failures, inadequate feedback, and inappropriate fallbacks. Delegates to the silent-failure-hunter subagent for isolation

πŸ”Œ
exploreπŸ”ŒPlugin

Map the terrain before designing: locate, trace, pattern, constrain. Used before any substantive design or planning step. Output is mostly for the agent's grounding; only surprises and hard constraints surface to the user.

πŸ”Œ
design-optionsπŸ”ŒPlugin

Generate multiple strong design options with explicit tradeoff profiles, starting from the ideal architecture.

πŸ”Œ
verify-resultπŸ”ŒPlugin

Black-box verification of any agent output: code, documents, presentations, reports, configs. Examine from the consumer's perspective and show evidence.