memex/projects/org-skill-tech-analyst/PRD.org

PRD: Skill - Technical Analyst Agent

• 1. Purpose
• 2. User Needs
  • 2.1 Protocol Perception
  • 2.2 TDD Inception (Success Criteria)
  • 2.3 Automated Test Execution (Initial)
  • 2.4 Structural Enforcement
• 3. Success Criteria

1. Purpose

Define the automated testing and analysis behaviors for the PSF Consensus Loop. The Technical Analyst skill transforms a SIGNED PROTOCOL (Blueprint) into a comprehensive, failing TDD suite (Success Criteria).

2. User Needs

2.1 Protocol Perception

As the system orchestrator, I need the Analyst to identify when an architecture is ready for testing.

• The Analyst MUST monitor `$PROJECTS_DIR` for `PROTOCOL.org` files with `#+STATUS: SIGNED`.

2.2 TDD Inception (Success Criteria)

I need rigorous test cases generated from semantic interfaces.

• The Analyst MUST generate a test suite in the project's `tests/` directory.
• It MUST cover both the "Happy Path" and "Edge Case" scenarios.
• It MUST ensure that all tests match the function signatures defined in the project's `PROTOCOL.org`.

2.3 Automated Test Execution (Initial)

I need the Analyst to verify that the tests fail initially (Red-Green-Refactor).

• The skill must have a symbolic (Lisp) actuator that writes the generated test code and confirms its existence.

2.4 Structural Enforcement

I need the Analyst to ensure the project's `tests/` directory is correctly initialized.

• The Analyst MUST be able to scaffold the `tests/` directory if it is missing.

3. Success Criteria

• Trigger Accuracy: Analyst correctly identifies a `SIGNED` PROTOCOL and ignores `DRAFT` Protocols.
• TDD Suite Generation: Analyst generates a test suite that references at least one interface from the PROTOCOL.
• Physical Inception: The generated test code is physically written to `tests/test-suite.lisp` (or equivalent).
• Edge Case Coverage: The generated suite includes at least one negative test case (error handling).