32 lines
1.6 KiB
Org Mode
32 lines
1.6 KiB
Org Mode
#+TITLE: PRD: Skill - Architect Agent
|
|
#+STATUS: FROZEN
|
|
#+AUTHOR: Agent
|
|
#+CREATED: [2026-03-31 Tue 12:15]
|
|
|
|
* 1. Purpose
|
|
Define the automated architectural behaviors for the PSF Consensus Loop. The Architect skill transforms a FROZEN PRD (Demand) into a rigorous PROTOCOL (Blueprint).
|
|
|
|
* 2. User Needs
|
|
|
|
** 2.1 PRD Perception
|
|
As the system orchestrator, I need the Architect to identify when a project is ready for blueprinting.
|
|
- The Architect MUST monitor `$PROJECTS_DIR` for `PRD.org` files with `#+STATUS: FROZEN`.
|
|
|
|
** 2.2 Semantic Translation
|
|
I need ambiguous requirements translated into executable interfaces.
|
|
- The Architect MUST generate `PROTOCOL.org` with Lisp-style function signatures for all core requirements.
|
|
- It MUST define the "Architectural Intent" to maintain long-term system integrity.
|
|
|
|
** 2.3 Institutional Memory Integration
|
|
I need architectural decisions to be grounded in experience.
|
|
- The Architect MUST reference `notes/institutional-memory.org` when making significant design choices.
|
|
|
|
** 2.4 Physical Actuation
|
|
I need the blueprint to be physically written to the project directory.
|
|
- The skill must have a symbolic (Lisp) actuator that writes the generated Org content to the disk.
|
|
|
|
* 3. Success Criteria
|
|
- [ ] **Trigger Accuracy:** Architect correctly identifies a `FROZEN` PRD and ignores `DRAFT` PRDs.
|
|
- [ ] **Protocol Generation:** Architect generates a `PROTOCOL.org` that contains at least one valid Lisp interface signature.
|
|
- [ ] **File Integrity:** The generated `PROTOCOL.org` is syntactically valid Org-mode and contains the correct front matter (`#+TITLE`, `#+STATUS: DRAFT`).
|