Why does this skill require the /understanding skill first?

The aligning skill is designed to own zero rules itself; it reads all conformance rules and templates from the 'understanding' skill's directory to ensure audit consistency across a project.

What is 'atemporal voice' in this context?

Atemporal voice is a writing style that ensures documentation remains accurate over time by avoiding temporal markers like 'we will,' 'currently,' or 'previously.' This skill audits text to ensure it describes the system state as a persistent fact.

Which file types are recognized by the aligning skill?

It recognizes specific extensions and directory patterns including .adr.md (Decision Records), .pdr.md (Product Decisions), .prd.md/.product.md, and spec files within .enabler/ or .outcome/ directories.

Can this skill automatically fix my documentation errors?

No. Following its 'Facts Only' principle, the skill identifies and reports violations of rules but does not suggest fixes or rewrite content, allowing the user to maintain full control over the documentation.

Spec Tree Alignment

Name: Spec Tree Alignment
Author: outcomeeng

byoutcomeeng

•

Aprendizaje y Documentación

Audits specification files for structural conformance, atemporal voice, and proper content placement within a Spec Tree hierarchy.

The Spec Tree Aligning skill is a specialized auditing utility that ensures project documentation adheres to strict organizational standards. It performs multi-dimensional checks on markdown files, verifying that headings match predefined templates, language remains 'atemporal' (free of time-based markers like 'currently' or 'will'), and content is placed in the correct artifact type. By acting as a factual linter for specs, enablers, and decision records (ADRs/PDRs), it helps maintain a durable and accurate project map that stays relevant throughout the software lifecycle.

Características Principales

01Atemporal Voice Audit: Scans for temporal markers and narration that date documentation or describe future intentions.

02Placement Validation: Detects when technical approaches, product decisions, or code-level details are in the wrong file type.

03Strict Classification: Automatically identifies enablers, outcomes, and decision records based on directory suffixes and naming conventions.

04Template Conformance: Validates headings and sections against standard ADR, PDR, and product templates.

051 GitHub stars

06Factual Reporting: Generates objective findings without subjective severity ratings to maintain audit integrity.

Casos de Uso

01Cleaning up legacy documentation by identifying misplaced implementation details that belong in code.

02Auditing newly created ADRs or specs for structural alignment with team standards.

03Reviewing project documentation before a release to ensure it reflects a durable, atemporal state.

Características Principales

01Atemporal Voice Audit: Scans for temporal markers and narration that date documentation or describe future intentions.

02Placement Validation: Detects when technical approaches, product decisions, or code-level details are in the wrong file type.

03Strict Classification: Automatically identifies enablers, outcomes, and decision records based on directory suffixes and naming conventions.

04Template Conformance: Validates headings and sections against standard ADR, PDR, and product templates.

051 GitHub stars

06Factual Reporting: Generates objective findings without subjective severity ratings to maintain audit integrity.

Casos de Uso

01Cleaning up legacy documentation by identifying misplaced implementation details that belong in code.

02Auditing newly created ADRs or specs for structural alignment with team standards.

03Reviewing project documentation before a release to ensure it reflects a durable, atemporal state.