speclan

Plugin speclan from marketplace digital-dividend-marketplace in thlandgraf/cc-marketplace. Commands read from the repo's manifest — 1 month ago.

Skills (11)

• run-speclan-id-generator

  Run, smoke-test, and verify the speclan-id-generator CLI (generate-id.mjs) — the tool that mints SPECLAN entity IDs (G-###, F-/R-/CR-####). Use when asked to "run the id generator", "test generate-id", "verify the ID gap", "check ID generation", or after changing the end-biased gap constants or the

• SPECLAN Ask

  Answer questions about SPECLAN specifications with full context — relationships, hierarchy, status, and cross-references rather than just reading a single file. Use whenever someone asks about a feature, requirement, goal, change request, or references a SPECLAN entity ID (G-###, F-####, R-####, CR-

• check-speclan-tree

  This skill should be used when the user asks to "check the speclan tree", "validate specs", "lint speclan", "verify spec consistency", "audit the speclan directory", "find broken spec links", "check for duplicate IDs", "check ID format", "find misplaced requirements", or otherwise wants a SPECLAN tr

• SPECLAN Grill

  Grilling session that stress-tests SPECLAN specifications through a relentless one-question-at-a-time interview. Its core duties: reduce ambiguities, clarify contradictions (spec vs spec, spec vs code), and close definition gaps — undefined terms, vague language, missing edge cases — before specs ge

• SPECLAN Implement Manual

  This skill should be used when the user asks to "implement next feature", "implement manual", "continue implementation", "implement-manual", "pick up the plan", "implement from plan", or wants to implement the next undone item from a manual implementation plan file. Picks up a plan file created by t

• SPECLAN Plan Manual

  This skill should be used when the user asks to "plan manual implementation", "create a manual plan", "list approved specs for implementation", "plan-manual", "show approved requirements", "prepare implementation plan", or wants to generate a plan file listing all approved SPECLAN requirements ready

• SPECLAN Review Manual

  This skill should be used when the user asks to "review plan", "review implementations", "review manual", "review-manual", "review from plan", "check all implementations", or wants to review all in-review items from a manual implementation plan file. Picks up a plan file created by the plan-manual s

• SPECLAN Format

  This skill should be used when the user works with SPECLAN specification files in the speclan/ directory, asks to "read a feature", "list requirements", "create a feature", "new requirement", "update a spec", "delete a change request", "show spec hierarchy", "ID format", or references SPECLAN entity

• SPECLAN ID Generator

  Generates unique, collision-free IDs for SPECLAN entities (Goal G-###, Feature F-####, Requirement R-####, ChangeRequest CR-####). Use this skill whenever a new entity is being created or added anywhere under the speclan/ directory — creating a feature, adding a requirement, nesting a sub-feature, f

• SPECLAN Query

  This skill should be used when the user asks to "list features", "find requirements", "show approved specs", "get children of a feature", "index specs", "query specs by status", or needs to search, filter, or programmatically query SPECLAN entities by type, status, or parent relationship.

• Sync Specs from Session

  This skill should be used when the user asks to "sync specs", "update specs from work", "record what we did", "add to speclan", "document implemented features", or wants to capture session work as SPECLAN specifications. Analyzes conversation context to identify implemented features and syncs with s

Slash commands (13)

• /speclan:ask

  Ask about any SPECLAN entity — get holistic context with hierarchy, relationships, status, and change requests

• /speclan:from-bmad

  Convert BMAD-METHOD planning artifacts to SPECLAN format

• /speclan:from-speckit

  Convert speckit specifications to SPECLAN format

• /speclan:grill

  Grill the user on SPECLAN specs — relentless one-question-at-a-time interview that reduces ambiguities, clarifies contradictions, and closes definition gaps before approval

• /speclan:implement-custom:sequential

  Sequential implementation strategy for custom planfiles. Implements items one by one in dependency order with cross-session CLAUDE.md knowledge bridging, structured logging, tests, and milestone reviews. Use after priming a session with a SPECLAN custom planfile. Sequential is the right choice for c

• /speclan:implement-manual

  Implement the next feature from a manual implementation plan

• /speclan:plan-manual

  Create a manual implementation plan from approved SPECLAN specifications

• /speclan:review-manual

  Review all in-review items from a manual implementation plan

• /speclan:status

  Check SPECLAN project setup, installed plugins, and specification statistics

• /speclan:sync-from-session

  Sync SPECLAN specs from session work - identifies implemented features and updates specs

• /speclan:to-bmad-prd

  Generate a BMAD-standard PRD directly from approved SPECLAN specifications (standalone converter, no BMAD skills required)

• /speclan:to-bmad

  Generate a BMAD-standard PRD from approved SPECLAN specs using BMAD's native PRD creation workflow

• /speclan:to-speckit

  Inject approved SPECLAN Features into speckit for specification processing

Subagents (7)

• architecture-reviewer

  Use this agent to review architectural quality of implementation files. Analyzes design patterns, SOLID principles, coupling, module boundaries, dependency direction, and separation of concerns. Returns categorized findings with file:line evidence.

• bmad-converter

  Use this agent when the user wants to convert specifications between BMAD-METHOD and SPECLAN formats. Examples:

• code-hygiene-reviewer

  Use this agent to review code hygiene and structural quality of implementation files. Analyzes naming conventions, duplication, dead code, type safety, error handling patterns, and other structural concerns. Returns categorized findings with file:line evidence.

• feature-verifier

  Use this agent when the user wants to verify features are implemented correctly, check implementation against feature specs, or needs a verification report. Examples:

• implementation-order

  Use this agent to determine optimal implementation order for features, requirements, or change requests by analyzing dependencies. Returns an ordered list. Called by plan-manual and implement commands — not typically invoked directly.

• requirement-verifier

  Use this agent when the user wants to verify a requirement is implemented, check if a specific requirement is satisfied, or verify implementation against requirement specs. Examples:

• speckit-converter

  Use this agent when the user wants to convert specifications between speckit and SPECLAN formats. Examples:

Hooks (2)

• SessionStart

  node $CLAUDE_PLUGIN_ROOT/hooks/scripts/detect-context.mjs

• PreToolUse

  node $CLAUDE_PLUGIN_ROOT/hooks/scripts/guard-locked-specs.mjs

Similar plugins