spec-tree

Run the spec-tree TDD flow on a subtree or discover work from spx/EXCLUDE

Author a spec tree artifact (product, ADR, PDR, enabler, outcome)

Set up a new spec tree for this project

Gather requirements through questioning before executing a task

Commit following Conventional Commits

<context>

Load a handoff document to continue previous work

Reflect, persist, and close session without creating a handoff file

Stop ad hoc work and follow the spec-tree methodology

Autonomous TDD agent. Runs the full spec-tree 8-phase flow on a node with three audit gates. Use when the user passes --agent to /apply.

ALWAYS invoke this skill when reviewing, auditing, or checking spec file conformance. NEVER check spec conformance without this skill.

ALWAYS invoke this skill before implementing any spec-tree work item. NEVER write code for a spec-tree node without this skill.

ALWAYS invoke this skill when auditing PDRs or after writing a PDR. NEVER audit PDRs without this skill.

ALWAYS invoke this skill when auditing test evidence quality, after writing tests for a spec node, or before closing an outcome.

ALWAYS invoke this skill when adding, defining, or creating specs, decisions, or nodes. NEVER author spec tree artifacts without this skill.

ALWAYS invoke this skill when setting up a new spec tree or when /authoring detects an empty spx/ directory. NEVER create a spec tree from scratch without this skill.

ALWAYS invoke this skill when committing changes or when user says "commit". NEVER run git commit without this skill.

ALWAYS invoke this skill when asking about status, progress, or what exists in the spec tree. NEVER work on any part of the spec tree without loading context through this skill first.

ALWAYS invoke this skill when breaking down, splitting, scoping, or structuring spec tree nodes. NEVER decompose specs without this skill.

ALWAYS invoke this skill when moving nodes, re-scoping content, or extracting shared enablers. NEVER restructure the spec tree without this skill.

ALWAYS invoke this skill before writing tests or when learning the testing approach.

ALWAYS invoke this skill before any spec-tree work to load methodology. NEVER create, read, or modify spec tree files without loading this foundation first.