doc-flow

Select artifact-specific skills across the 16-layer SDD workflow.

16|3|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-flow
Source: https://github.com/vladm3105/aidoc-flow-framework/tree/main/.claude/skills/doc-flow
Command: npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as the orchestrator for the AI-Driven Specification-Driven Development (SDD) workflow. It provides guidance on which artifact-specific skill to use next, offers a complete 16-layer SDD architecture overview, and explains general SDD principles to reduce decision fatigue and complexity.

Core Features & Use Cases

  • Skill Selection Guidance: Helps determine which artifact-specific skill to use based on your current artifact and workflow stage.
  • Workflow Overview: Presents the complete 16-layer SDD architecture and how artifacts flow from Strategy to implementation.
  • Integration Guidance: Explains how artifact skills interconnect and how to move smoothly through the workflow.

Quick Start

Use the doc-flow skill to get a recommended path when starting a brand-new SDD project or when you’re unsure which artifact to create first. For example, ask: "Doc-flow, what is the next recommended skill after BRD?"

Frequently Asked Questions about doc-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right skill for each stage of a specification-driven development workflow?

Doc-flow guides skill selection across the 16-layer SDD workflow, from Strategy artifacts (BRD, PRD) through implementation and testing phases. It maps your current artifact to the next recommended skill, eliminating guesswork about which tool to use at each workflow stage.

What is the complete architecture of a specification-driven development workflow?

SDD spans 16 layers: BRD, PRD, EARS, BDD, ADR, SYS, REQ, IMPL, CTR, SPEC, TASKS, IPLAN, ICON, and REF. Doc-flow presents this full architecture, showing how artifacts flow from strategy through implementation and explaining how each layer connects to maintain traceability.

How do artifact skills integrate within an SDD workflow?

Doc-flow explains integration rules and structured skill-selection processes anchored to standardized traceability practices. It shows how artifact-specific skills interconnect and provides guidance for moving smoothly between workflow stages without losing context.

What's the next recommended artifact to create after completing a BRD in SDD?

Doc-flow recommends the next artifact based on your current position in the 16-layer workflow. After BRD, it typically guides you toward PRD or EARS depending on your project context, with integration guidance for seamless transition.

Can I use doc-flow to start a new specification-driven development project from scratch?

Yes. Doc-flow provides structured guidance for brand-new SDD projects, presenting the complete workflow architecture and recommending the initial artifacts and skills to begin with, reducing decision fatigue at project start.

Does doc-flow enforce traceability practices across the SDD workflow?

Doc-flow anchors guidance to standardized traceability practices and the SPEC_DRIVEN_DEVELOPMENT_GUIDE.md, ensuring that skill selection and artifact flow maintain consistent traceability throughout the entire 16-layer SDD workflow.