Why are technical details forbidden in IMPL documents?

Technical 'how-to' details belong in SPEC documents. Keeping IMPL documents focused on strategy ensures high-level alignment without getting lost in code-level details.

What traceability links does this skill validate?

It checks for required references to upstream documents including BRDs, PRDs, EARS, BDD, ADRs, and System (SYS) requirements.

How do I invoke the validation process?

You can request validation by asking Claude to check a specific IMPL file or it can trigger automatically after you create or modify implementation artifacts.

What does Layer 8 mean in this context?

Layer 8 refers to the specific architectural layer within the aidoc-flow-framework that handles project management and implementation strategy documentation.

What is an IMPL document?

An IMPL (Implementation Approach) document defines the project context, strategy, and phased breakdown, focusing on the who, what, when, and why of a project.

IMPL Documentation Validator

Name: IMPL Documentation Validator
Author: vladm3105

byvladm3105

•

Aprendizaje y Documentación

Validates Implementation Approach (IMPL) documents to ensure adherence to Layer 8 architectural and project management standards.

This skill automates the validation of Implementation Approach (IMPL) artifacts within the AI Doc Flow framework. It ensures that planning documents maintain a strict focus on project context, phased strategy, risk management, and traceability while preventing technical implementation details from leaking into high-level planning. By enforcing Layer 8 schema standards, it helps development teams maintain consistent document structures, accurate metadata, and robust cross-document traceability between requirements, specifications, and execution tasks.

Características Principales

01Automated Layer 8 schema validation for IMPL documents

02Cross-document traceability checking for BRD, PRD, and ADR links

03Automated risk register and phase table auditing

04Detailed error reporting with severity-coded feedback

051 GitHub stars

06Strict enforcement of 4-part document structure and metadata

Casos de Uso

01Auditing risk registers and phase timelines for consistency in large-scale projects

02Verifying project implementation plans before transitioning to technical specifications

03Ensuring compliance with architectural standards across distributed documentation sets

Características Principales

01Automated Layer 8 schema validation for IMPL documents

02Cross-document traceability checking for BRD, PRD, and ADR links

03Automated risk register and phase table auditing

04Detailed error reporting with severity-coded feedback

051 GitHub stars

06Strict enforcement of 4-part document structure and metadata

Casos de Uso

01Auditing risk registers and phase timelines for consistency in large-scale projects

02Verifying project implementation plans before transitioning to technical specifications

03Ensuring compliance with architectural standards across distributed documentation sets