skills.rest
labs21-dev
labs21-devOFFICIAL
Explore all skills by this author →
GitHub

plan

Design AI workstream architecture with data flows, API schemas, and test strategy.

28|2|Updated Feb 5, 2026
Search Tags:#design#architecture#plan#system-design#workstream#spec-traceability
One-click install
npx skills add https://github.com/labs21-dev/agents-stack --skill plan-labs21-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/labs21-dev/agents-stack/tree/main/templates/.agents/skills/using-agents-stack/plan
Command: npx skills add https://github.com/labs21-dev/agents-stack --skill plan-labs21-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and architecture for AI workstreams can drift from the SPEC, risking misaligned implementation. This Skill provides a structured blueprint to capture decisions, traceability, and risk analysis before any code is written.

Core Features & Use Cases

  • Architecture decision logging with traceability to SPEC sections.
  • Data flow and API surface planning for planned components.
  • Impact analysis mapping real code files to plan changes for safe rollouts.

Quick Start

Create the plan.md at .agents-stack/workstream/<ws-id>_{YYYYMMDD}/plan.md and fill it with architecture decisions grounded in the SPEC.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I design architecture for AI workstreams aligned with SPEC requirements?▼

Designing architecture for AI workstreams involves detailing components, data flows, and interfaces. This ensures traceability and impact analysis by mapping architecture decisions directly to SPEC requirements before implementation begins.

What is the best way to map code files to architecture plan changes for safe rollouts?▼

Mapping code files to plan changes is achieved through impact analysis. This process identifies potential risks by linking real code files to planned architecture modifications, ensuring safe and structured rollouts.

How do I create a plan with API schemas and DB models for a workstream?▼

Creating a plan with API schemas and DB models requires defining data flows and interface surfaces for planned components. This structured blueprint captures architectural decisions in a plan.md file during the planning phase.

Can I log architecture decisions with traceability to specific SPEC sections?▼

Logging architecture decisions with traceability to SPEC sections is fully supported. This feature captures decisions in a structured blueprint, preventing workstream drift and maintaining alignment with the original specifications.

Why does AI workstream architecture drift from the SPEC during implementation?▼

Architecture drifts from the SPEC when planning lacks a structured blueprint to capture decisions and traceability. Without mapping data flows and interfaces to SPEC sections, implementation risks misalignment with original requirements.

Do I need to define test strategy during the architecture planning phase?▼

Defining test strategy is a core part of architecture planning. Scoping includes plan, API schemas, DB models, and test strategy for a workstream, ensuring comprehensive coverage before any code is written.

Related Skills

Explore More Software Engineering Skills→
HechaoYannetHechaoYannet

create-architecture

Generate a master architecture document from GDDs, ADRs, and governance constraints.

Community
Advanced
susantosantosusantosanto

superpowers-writing-plans

Translate approved specs into structured implementation plans with tasks and architecture.

Community
Intermediate
BellaBeBellaBe
37

foundation-schema

Validate LeanOS artifact manifests in artifacts/vN/ against foundation-schema definitions and cross-references.

Community
Advanced
RdindaRdinda
1

reversa-architect

Generate C4 diagrams, ERD, integration maps, and spec impact matrices from legacy analysis.

Community
Advanced