SW Design and Development
A complete pipeline of expert prompts for the end-to-end software development lifecycle, from initial PRD discovery to architectural design, technical orchestration, and audit logging.
How to use
Execute the software design and development pipeline sequentially by starting with requirements co-creation, moving through system architecture and design scaffolding, and wrapping up with the developer orchestrator and post-session audit logging.
1. Requirements & System Architecture
Establish the authoritative source of truth and map out the system boundaries before writing any code.
PRD Co-Creation — Guided Discovery
Guides you through an interactive Q&A discovery session to compile a structured Product Requirements Document (PRD) specifying target personas, functional and non-functional requirements, and project scope boundaries to serve as a development blueprint.
System Architecture Design
Generates a comprehensive system architecture design detailing load balancing, caching layers, data flow patterns, and capacity estimations based on a Product Requirements Document (PRD) to establish solid system boundaries.
System Design Document — C4 Model
Generates a detailed system design document detailing business posture, security controls, and risk assessments, accompanied by visual Context, Container, and Deployment architecture diagrams mapped via Mermaid syntax to guide developer implementation.
2. Planning & Effort Estimation
Break down implementation phases into modular steps and estimate timeline complexity to prevent scope creep.
Implementation Planning & Scaffolding
Generates a phased software implementation plan, directory structure, file explanations, and fully documented source code scaffolds based on system design, architecture, and requirements artifacts to guide initial development.
Level of Effort Estimator
Generates a structured Level of Effort (LOE) document estimating software implementation timelines, team dependencies, resource requirements, and technical risk mitigations based on design artifacts to establish project milestones.
3. Active Orchestration
Run the lead technical developer agent to write code step-by-step based on the generated design blueprints.
Developer Workflow Orchestrator
Establishes a Senior Technical Architect and Lead Developer persona to direct active code implementation, prioritizing project configuration constraints, implementation plans, and functional requirements within a privacy-first, local-only development cycle.
4. Post-Session Audit Trail
Document session metrics, architectural decisions, and the chronological development history to maintain repository health.
Development Session Metrics Auditor
Synthesizes raw development session logs, token usage statistics, and wall-clock times into a structured metrics table calculating AI-to-human acceleration ratios to document lifecycle efficiency across software project phases.
Architectural Decision Log Writer
Documents the cognitive reasoning, design trade-offs, and logical hierarchies behind software engineering choices to establish a transparent, audit-ready architectural decision log that tracks system architecture evolution across project development phases.
Engineering Session Chronicle Log
Reconstructs a chronological timeline of a software development session, capturing the transitions between automated AI code generation and manual human code stabilization to preserve precise project engineering history and key session milestones.