# SPECLAN

> SPECLAN is a VS Code extension for specification engineering. It provides a layered, Git-native framework for turning ideas into traceable, machine-processable specifications with AI agents that do the heavy lifting.

SPECLAN treats specifications as first-class engineering artifacts stored as Markdown files with YAML frontmatter directly in your repository. The entity hierarchy flows from Goals through Features (with hierarchical sub-features) down to Requirements. AI agents generate, refine, and validate specifications on your behalf. Full traceability links every requirement back to a business goal.

- Website: https://speclan.net
- GitHub: https://github.com/digital-dividend/speclan
- Install: `code --install-extension DigitalDividend.speclan-vscode-extension`

## About

- [Home](https://speclan.net/): Landing page with overview, workflow, and key features
- [Features](https://speclan.net/features/): Detailed feature descriptions including layered specs, Git-native workflow, AI agents, and traceability
- [About SPECLAN](https://speclan.net/about/): Mission, origin story, design principles, and technology stack

## Documentation

- [Getting Started: New Project](https://speclan.net/help/getting-started/greenfield/): You have a new project idea. No code yet. No specs. Just an idea and the motivation to build something.
- [Getting Started: Existing Project](https://speclan.net/help/getting-started/brownfield/): You have a project. It has code, it has history, it has momentum. Now you want to bring structure to what comes next.
- [Goals](https://speclan.net/help/concepts/goals/): Goals (G-###) represent high-level business objectives. They are the starting point of the SPECLAN specification hierarc
- [Features](https://speclan.net/help/concepts/features/): Features (F-####) describe specific capabilities of the system. They form a hierarchical tree and can contain sub-featur
- [Requirements](https://speclan.net/help/concepts/requirements/): Requirements (R-####) define specific, testable conditions that a feature must satisfy. They belong to exactly one featu
- [Requirements Workflow](https://speclan.net/help/workflows/requirements-workflow/): The requirements workflow governs how SPECLAN specifications progress from initial creation through to approval. This pr
- [Development Workflow](https://speclan.net/help/workflows/development-workflow/): The development workflow covers the transition of SPECLAN specifications from **approved** to **under-test** status. Thi
- [QA Workflow](https://speclan.net/help/workflows/qa-workflow/): The QA workflow covers the final verification phase where the QA team validates completed development work and transitio
- [Change Requests](https://speclan.net/help/workflows/change-requests/): Change Requests (CRs) are the formal mechanism for proposing modifications to SPECLAN specifications that have progresse
- [Entity Types](https://speclan.net/help/reference/entity-types/): SPECLAN uses a layered hierarchy of entity types. Features can be nested to create hierarchical sub-feature trees:
- [Status Lifecycle](https://speclan.net/help/reference/status-lifecycle/): Every SPECLAN entity follows a defined status progression:

## Optional

- [Community Discussions](https://github.com/thlandgraf/speclan-essentials/discussions/1): Ask questions, share your experience, and connect with other SPECLAN users. Whether you are just getting started or pushing the boundaries — the community is here to help.
- [Issue Tracker](https://github.com/thlandgraf/speclan-essentials/issues): Found something broken? Have an idea that would make SPECLAN better? Open an issue on GitHub and help us improve.
- [Contact](https://speclan.net/contact/): Support and general inquiry contact information