speclan

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

Review all in-review items from a manual implementation plan

Check SPECLAN project setup, installed plugins, and specification statistics

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

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

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

Inject approved SPECLAN Features into speckit for specification processing

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.

Verify that a SPECLAN requirement is correctly implemented in the codebase.

You are a specification format converter specializing in bidirectional transformation between speckit and SPECLAN formats.

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.

This skill should be used when the user needs to generate IDs for SPECLAN entities, asks to "generate an ID", "new feature ID", "unique requirement ID", "create a collision-free ID", or when any command or agent needs to assign IDs to new SPECLAN entities.

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.

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 speclan directory.

2 hooks across 2 events