By thlandgraf
Manage project specifications as structured interlinked markdown files using SPECLAN methodology. Generate implementation plans from approved specs, track progress with checklists, and verify code compliance against specifications.
Ask about any SPECLAN entity — get holistic context with hierarchy, relationships, status, and change requests
Convert BMAD-METHOD planning artifacts to SPECLAN format
Convert speckit specifications to SPECLAN format
Implement the next feature from a manual implementation plan
Create a manual implementation plan from approved SPECLAN specifications
Analyze source files for architectural and design quality. Focus on how components are structured and interact, independent of specifications.
You are a specification format converter specializing in bidirectional transformation between BMAD-METHOD and SPECLAN formats.
Analyze source files for structural code quality issues. Focus on the code as written, independent of specifications.
Deeply verify that SPECLAN features are correctly implemented in the codebase.
Analyze dependencies between features or requirements and determine optimal implementation order. Return a sorted list — nothing more.
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-####). Also use when users ask about project status, what's ready to implement, dependency chains, or want an overview of their spec hierarchy — even if they don't explicitly say "SPECLAN" or "spec". Any question that needs context from the speclan/ directory should route here.
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 the plan-manual skill and implements items one at a time.
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 for manual implementation.
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 skill and reviews ALL [?] items at once, verifying spec compliance and code quality.
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 types (Goal, Feature, Requirement, ChangeRequest). Provides foundational knowledge for all speclan/ directory operations including file structure, validation rules, status lifecycle, and entity relationships.
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Has parse errors
Some configuration could not be fully parsed
Has parse errors
Some configuration could not be fully parsed
Claude Code plugins for specification-driven development, project governance, and task management.
This repo is intended to be cloned and customized to fit your software development process. Fork it, adjust the plugins to match your workflows, and use it as a starting point rather than a fixed dependency.
Claude Code helper for the SPECLAN VSCode extension - manage project specifications as interlinked markdown files.

Using BMAD? See the BMAD Integration Guide for a full walkthrough of the round-trip workflow between BMAD and SPECLAN.
| Flow | Description |
|---|---|
| Ask | Query specs with full context — hierarchy, relationships, status |
| Impl → Spec | Sync session work to SPECLAN specifications |
| Spec → Impl | Plan, implement, and review approved specs (manual three-phase workflow) |
| BMAD → Speclan | Convert BMAD planning artifacts (PRD, Epics) to SPECLAN format |
| Speclan → BMAD | Generate BMAD-standard PRD from approved specs (two approaches: BMAD-native or standalone converter) |
| Speckit → Speclan | Convert speckit specifications to SPECLAN format |
| Speclan → Speckit | Inject approved SPECLAN specs into speckit commands |
| Command | Description |
|---|---|
/speclan:ask | Ask about any SPECLAN entity — get holistic context with hierarchy, relationships, and status |
/speclan:status | Check project setup, installed plugins, and spec statistics |
/speclan:sync | Sync session work to SPECLAN specs - identifies implemented features |
/speclan:plan-manual | Create a manual implementation plan from approved specs |
/speclan:implement-manual | Implement the next pending item from a manual plan |
/speclan:review-manual | Review all in-review items, verify spec compliance and code quality |
/speclan:from-bmad | Convert BMAD planning artifacts (PRD, Epics, Architecture) to SPECLAN format |
/speclan:to-bmad | Generate BMAD-standard PRD using BMAD's native PRD creation workflow |
/speclan:to-bmad-prd | Generate BMAD-standard PRD using standalone converter (no BMAD skills required) |
/speclan:from-speckit | Convert speckit specs to SPECLAN format |
/speclan:to-speckit | Inject approved SPECLAN Features into speckit |
| Agent | Description |
|---|---|
feature-verifier | Deep 5-layer verification of feature implementation against specs |
requirement-verifier | Verify individual requirements are satisfied by code |
implementation-order | Analyze feature dependencies and determine optimal build order |
bmad-converter | Bidirectional conversion between BMAD-METHOD and SPECLAN formats |
speckit-converter | Bidirectional conversion between speckit and SPECLAN formats |
code-hygiene-reviewer | Review code structure, naming, duplication, dead code, type safety |
architecture-reviewer | Review design patterns, SOLID principles, coupling, module boundaries |
| Skill | Description |
|---|---|
speclan-format | Foundational knowledge for all speclan/ file operations |
speclan-query | Query specs by type, status, or parent relationship (JSON output) |
speclan-id-generator | Collision-free random ID generation for SPECLAN entities |
ask | Answer spec questions with full context — hierarchy, relationships, status |
sync-from-session | Workflow for capturing session work as SPECLAN specs |
plan-manual | Create manual implementation plans from approved specs |
implement-manual | Implement next item from a manual plan (plan → implement → review) |
review-manual | Review all in-review items, verify spec compliance and code quality |
| Event | Behavior |
|---|---|
SessionStart | Detects speclan/ directory, counts specs, checks plugin dependencies |
PreToolUse (Write/Edit) | Guards locked specs - blocks direct edits to in-development/released/deprecated entities, rejects invalid status values |
Three-phase workflow for implementing approved specs with human oversight at each stage:
/speclan:plan-manual → /speclan:implement-manual → /speclan:review-manual
1. Plan — /speclan:plan-manual queries all approved specs and generates a plan file at speclan/.local/plans/. The plan is a pure-data checklist with checkbox states tracking progress. Only approved items and their ancestor chain are included.
2. Implement — /speclan:implement-manual picks up the plan file and implements the next [ ] item. Run repeatedly — each invocation implements one feature (with all its requirements) or one individual item. Checkboxes transition: [ ] → [~] → [?].
npx claudepluginhub thlandgraf/cc-marketplace --plugin speclanFilesystem-based task management with git integration - track tasks through open/wip/done lifecycle
Manage project constitution files - rules, best practices, patterns, and guardrails for LLM/coding agents
Multi-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Memory compression system for Claude Code - persist context across sessions