What is 'atemporal voice' in requirements?

It is a documentation style that describes the product's ideal state as a permanent truth, avoiding phrases like 'Currently' or 'In the next phase' to ensure the PRD remains a durable reference.

Does it generate actual test code?

Yes, it maps every user capability to acceptance test scenarios, providing Gherkin steps and E2E code samples in TypeScript or Python to guide development.

Can I use it for existing projects?

Absolutely. It includes a context-reading protocol to scan your project structure and existing PRDs before proposing new requirements or features.

What makes this PRD skill different from a standard AI prompt?

It follows a rigorous multi-phase workflow involving root-cause analysis, mandatory user validation, and a specific three-level testing methodology to ensure requirements are actionable.

PRD Architect

Name: PRD Architect
Author: simonheimlicher

bysimonheimlicher

•

Productivity & Workflow

Generates authoritative Product Requirements Documents focused on measurable user outcomes and three-level testing validation.

The PRD Architect skill transforms vague product ideas into rigorous, testable blueprints by prioritizing user value and measurable success. It guides developers through a systematic discovery process—analyzing root causes, validating customer journeys, and defining capabilities as quantifiable guarantees. By enforcing an atemporal 'product truth' voice and mapping every requirement to specific acceptance tests (Unit, Integration, and E2E), it ensures that documentation remains a permanent, actionable reference rather than a temporary narrative. This skill is essential for teams that want to eliminate ambiguity and ensure every line of code serves a verified user need.

Key Features

01Root Cause Discovery: Analyzes symptoms to identify core user pain points and customer journeys.

02Measurable Outcomes: Defines success through quantified metrics like 'X% improvement in Y'.

031 GitHub stars

04Atemporal Voice Enforcement: Ensures requirements describe product truth without temporal narratives or 'MVP' jargon.

05Integrated Quality Guardrails: Self-checks PRDs against readiness criteria and Gherkin-based acceptance patterns.

06Three-Level Testing Strategy: Maps user capabilities to specific Unit, Integration, and E2E test scenarios.

Use Cases

01Translating messy user feedback into structured, testable technical requirements.

02Establishing a durable source of truth for long-term product maintenance and scaling.

03Formalizing a new feature or capability before implementation begins.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add simonheimlicher/spx-claude writing-prd

For use in Claude.ai and ChatGPT

Download Skill