Trace only flows supported by source, docs, tests, or explicit user context.
Label inferred lifecycle steps as assumptions.
Keep the trace focused on primary flows. Do not add speculative components.
Do not modify source code.
User Story:As a developer, I want to provide a high-level feature idea and receive a structured, unambiguous PRD so that a junior developer can implement it with minimal oversight.
Layer 1: User Journey (Flowchart)
Layer 2: Component Architecture
Component
Logic Source
Responsibility
Key Reference
User Interface
System Prompt
Capture intent and selections
Prompt Entry
Clarification Processor
Rule: Process
Generate lettered/numbered questions
PRD Mode: Step 2
Generation Engine
Rule: Structure
Format data into standard PRD sections
PRD Structure
Storage Manager
Rule: Output
Write Markdown to specific directory
/tasks/prd-*.md
Layer 3: Sequence Diagram
Key Design Patterns Used:
Stateful Interaction: The system pauses for user feedback (Clarification Step) before proceeding to final generation, ensuring accuracy.
Template Method: The PRD follows a rigid, predefined structure regardless of the feature content to ensure consistency.
Persistence Ignorance: The logic focuses on document structure, while the storage rule dictates the final file path and naming convention.
Data Structures
Quick Reference
Event Triggers: User prompt containing "new feature" or "PRD".
File Format: Standard GFM (GitHub Flavored Markdown).
Error Handling: If requirements are ambiguous, the AI must re-trigger the clarification loop.
Validation: Final PRD must be legible by a "Junior Developer" profile.
Related Lifecycles
Task Decomposition: Converting a PRD into a tasks-prd-*.md file.
DAP Implementation: Creating a Deployment Action Plan for schema changes.
System Onboarding: Generating use_cases.md from repo analysis.
Next Step: I can now save this lifecycle trace to .planning/memory/system/001_lifecycle_prd_generation.md. Would you like me to finalize the file creation?
1---2name: application-lifecycle-trace3description: Show case application lifecycle4---56#### **Title: PRD Generation**78#### **Guardrails**910- Trace only flows supported by source, docs, tests, or explicit user context.11- Label inferred lifecycle steps as assumptions.12- Keep the trace focused on primary flows. Do not add speculative components.13- Do not modify source code.1415**User Story:** _As a developer, I want to provide a high-level feature idea and receive a structured, unambiguous PRD so that a junior developer can implement it with minimal oversight._1617---1819#### **Layer 1: User Journey (Flowchart)**2021---2223#### **Layer 2: Component Architecture**2425| Component | Logic Source | Responsibility | Key Reference |26| --------------------------- | ----------------- | -------------------------------------- | ------------------ |27| **User Interface** | System Prompt | Capture intent and selections | `Prompt Entry` |28| **Clarification Processor** | `Rule: Process` | Generate lettered/numbered questions | `PRD Mode: Step 2` |29| **Generation Engine** | `Rule: Structure` | Format data into standard PRD sections | `PRD Structure` |30| **Storage Manager** | `Rule: Output` | Write Markdown to specific directory | `/tasks/prd-*.md` |3132---3334#### **Layer 3: Sequence Diagram**3536**Key Design Patterns Used:**37381. **Stateful Interaction:** The system pauses for user feedback (Clarification Step) before proceeding to final generation, ensuring accuracy.392. **Template Method:** The PRD follows a rigid, predefined structure regardless of the feature content to ensure consistency.403. **Persistence Ignorance:** The logic focuses on document structure, while the storage rule dictates the final file path and naming convention.4142---4344#### **Data Structures**4546---4748#### **Quick Reference**4950- **Event Triggers:** User prompt containing "new feature" or "PRD".51- **File Format:** Standard GFM (GitHub Flavored Markdown).52- **Error Handling:** If requirements are ambiguous, the AI **must** re-trigger the clarification loop.53- **Validation:** Final PRD must be legible by a "Junior Developer" profile.5455---5657#### **Related Lifecycles**58591. **Task Decomposition:** Converting a PRD into a `tasks-prd-*.md` file.602. **DAP Implementation:** Creating a Deployment Action Plan for schema changes.613. **System Onboarding:** Generating `use_cases.md` from repo analysis.6263---6465**Next Step:** I can now save this lifecycle trace to `.planning/memory/system/001_lifecycle_prd_generation.md`. Would you like me to finalize the file creation?66---6768> **Install:** ``npx skills add ChristopherAlphonse/calphonse-skills --skill application-lifecycle-trace``
Run npx skillmds@latest add christopheralphonse/application-lifecycle-trace in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Show case application lifecycle It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
ChristopherAlphonse (@christopheralphonse) published this skill. Their other Agent Skills are listed on their SkillMD profile.
ChristopherAlphonse