Does SPECLAN Ask modify my specification files?

No, this is a read-only skill designed for exploration and analysis. To modify specs, you should use direct editing or specific implementation commands.

What is the benefit of 'Context Over Content'?

It ensures you understand how a requirement fits into the larger project goal, its dependencies, and any pending changes, rather than just reading a single file in isolation.

What entity types can I query with this skill?

You can query Goals (G), Features (F), Requirements (R), and Change Requests (CR) using their unique IDs, names, or slugs.

Can I see which requirements are ready for implementation?

Yes, you can ask for entities with an 'approved' status to see what is ready for the next phase of your workflow.

How does the skill find my SPECLAN project?

It utilizes an integrated detection script that automatically searches for the 'speclan/' directory within your workspace.

SPECLAN Spec Navigator

Name: SPECLAN Spec Navigator
Author: thlandgraf

bythlandgraf

•

Gestión de Contenido

Provides deep, contextual insights into SPECLAN specifications by analyzing entity relationships, hierarchy, and implementation status.

The SPECLAN Ask skill transforms standard file reading into a comprehensive knowledge engine for project specifications. Instead of simply providing raw text, it builds a complete contextual picture of any SPECLAN entity—be it a Goal, Feature, or Requirement—by mapping its parents, children, siblings, and active change requests. This skill is essential for developers and architects who need to understand the 'why' and 'where' of a requirement within a complex system hierarchy, ensuring that every query results in actionable project intelligence rather than just isolated data points.

Características Principales

01Automated dependency and hierarchy tree visualization

02Real-time status tracking and lifecycle rule analysis

037 GitHub stars

04Cross-reference and active Change Request (CR) history exploration

05Advanced filtering by entity type, ID, or development phase

06Contextual relationship mapping (Upward, Downward, and Sideways)

Casos de Uso

01Investigating the impact of a specific Requirement (R-####) on its parent Feature and Goals

02Understanding the full dependency chain and status of a specific module before starting development

03Generating an overview of all 'approved' features that are ready for implementation

Características Principales

01Automated dependency and hierarchy tree visualization

02Real-time status tracking and lifecycle rule analysis

037 GitHub stars

04Cross-reference and active Change Request (CR) history exploration

05Advanced filtering by entity type, ID, or development phase

06Contextual relationship mapping (Upward, Downward, and Sideways)

Casos de Uso

01Investigating the impact of a specific Requirement (R-####) on its parent Feature and Goals

02Understanding the full dependency chain and status of a specific module before starting development

03Generating an overview of all 'approved' features that are ready for implementation