Skip to content

ASDLC Alignment: Commands → Patterns

This document provides explicit traceability from commands to ASDLC patterns and pillars, helping users understand the methodology behind the factory.

Overview

The commands in this project implement ASDLC (Agentic Software Development Lifecycle) patterns and pillars. Each command serves as a specialized station in a Factory Architecture, uses Standardized Parts (schema-enforced structure), and implements Quality Control (validation gates).

Command Mapping

Command ASDLC Patterns ASDLC Pillar Description
/create-task The PBI, Agent Constitution Factory Architecture, Standardized Parts Creates PBIs with standardized anatomy; workflow station for task creation
/decompose-task The PBI, Context Gates Factory Architecture, Quality Control Decomposition workflow with information-density gate
/refine-task The PBI, Context Gates Factory Architecture, Quality Control Refinement step with Definition of Ready (DoR) as gate
/create-plan The Spec, The PBI Standardized Parts Creates Specs (permanent state) or Plans (transient delta)
/start-task The Spec, The PBI, Context Gates Factory Architecture, Quality Control Command station with pre-flight validation gates
/complete-task Constitutional Review, The Spec, The PBI, Context Gates Quality Control, Standardized Parts Review Gate with dual-contract validation (Spec + Constitution)
/create-test The Spec, Context Gates Quality Control, Standardized Parts Test generation as output gate; uses Contract scenarios from Spec
/review-code Adversarial Code Review, Constitutional Review, The Spec Quality Control Review Gate using Critic Agent for dual-contract validation
/mcp-status Context Gates Quality Control Pre-flight validation gate for other commands
/setup-asdlc Agent Constitution, The Spec Factory Architecture, Standardized Parts Repository initialization command that creates AGENTS.md template and directory structure

ASDLC Pillars

The three ASDLC pillars are implemented across the command set:

  • Factory Architecture: Specialized command stations that handle specific workflow phases

  • Standardized Parts: Schema-enforced commands with consistent structure and validation

  • Quality Control: Automated validation gates that ensure correctness before proceeding

Pattern Details

Core Patterns

  • The Spec: Living documents as permanent source of truth for features
  • The PBI: Transient execution units that reference permanent Specs
  • Context Gates: Architectural checkpoints that filter input context and validate output artifacts

Review Patterns

Governance Patterns

How Commands Implement ASDLC

The command mapping table above shows which patterns each command implements. Key implementation details:

  • Context Gates: Multiple commands implement validation checkpoints (see commands with Context Gates in the mapping table)
  • The Spec Pattern: Commands create, read, or validate against Specs (permanent state documents)
  • The PBI Pattern: Commands create or work with PBIs (transient execution units that reference Specs)
  • Constitutional Review: Commands validate against both functional requirements (Spec) and architectural values (Constitution)

External Resources

  • ASDLC.io - ASDLC methodology and patterns