What is Layer 8 in the SDD workflow?

Layer 8, or the IMPL artifact, is a stage in the Structured Design Document workflow that documents the implementation strategy, specifically identifying who is responsible, the delivery timeline, and the technical scope.

What is the difference between REQ and IMPL artifacts?

REQ (Layer 7) defines atomic technical requirements, while IMPL (Layer 8) defines the strategy and logistics for how those requirements will be built and by whom.

Does this skill require existing documentation?

Yes, it typically requires upstream artifacts from Layers 1-7 (such as BRD, PRD, ADR, and REQ) to ensure full traceability and provide the necessary context for implementation.

Is the IMPL document mandatory for every project?

No, the IMPL layer is optional. It is highly recommended for complex projects or team-based environments, but can be skipped for simpler, solo tasks.

How does doc-impl help with project risk management?

It includes a dedicated Risk Assessment section where developers must document potential implementation risks, their likelihood, impact, and specific mitigation strategies.

Implementation Approach Architect (Layer 8)

Name: Implementation Approach Architect (Layer 8)
Author: vladm3105

byvladm3105

•

生産性とワークフロー

Generates structured implementation strategy documents that define the resource allocation, timelines, and technical scope for software delivery.

概要

The doc-impl skill is a specialized component of the Structured Design Document (SDD) workflow, specifically designed to create 'Layer 8' Implementation Approach (IMPL) artifacts. It formalizes the transition from technical requirements to active development by documenting the WHO-WHEN-WHAT of a project: assigning responsibilities, defining milestones, and outlining technical strategies. By enforcing strict cumulative traceability across seven upstream layers—including business, product, and system requirements—it ensures that implementation remains perfectly aligned with the original architectural vision while proactively identifying risks and blockers.

主な機能

Standardized WHO-WHEN-WHAT implementation strategy framework
Automated validation scripts for document integrity and quality gates
Automated cumulative traceability tagging for Layers 1-7
Integrated risk assessment and mitigation planning
Technical approach mapping for architecture and technology choices
1 GitHub stars

ユースケース

Coordinating resource allocation and assignments across multi-developer teams
Mapping technical requirements to specific delivery phases and milestones
Establishing a formal audit trail from business logic to implementation strategy

概要

主な機能

Standardized WHO-WHEN-WHAT implementation strategy framework
Automated validation scripts for document integrity and quality gates
Automated cumulative traceability tagging for Layers 1-7
Integrated risk assessment and mitigation planning
Technical approach mapping for architecture and technology choices
1 GitHub stars

ユースケース

Coordinating resource allocation and assignments across multi-developer teams
Mapping technical requirements to specific delivery phases and milestones
Establishing a formal audit trail from business logic to implementation strategy