Create and maintain living system specifications through structured conversation.
npx skills add https://github.com/wrteam-jay/blueprint --skill blueprint-wrteam-jay
Please help me install this Agent Skill. Skill: blueprint Source: https://github.com/wrteam-jay/blueprint/tree/main/skills/blueprint Command: npx skills add https://github.com/wrteam-jay/blueprint --skill blueprint-wrteam-jay
This Skill addresses the friction caused by tribal knowledge, terminology drift, and the lack of a shared reference for how systems work, ensuring a single source of truth.
Use the blueprint skill to start building a spec from scratch through structured conversation.
High-intent search queries and answers about installing and using this skill.
A living product spec is a continuously updated system documentation source that captures behavior, actors, and terminology to prevent tribal knowledge drift and ensure a shared vocabulary across teams.
You create and maintain a living specification through structured conversation to elicit, distill, and review system requirements, user stories, scenarios, and domain models, ensuring alignment before development begins.
You document system terminology by building a shared vocabulary with precise definitions within a living spec, providing a single source of truth for product, engineering, and support teams to reference.
Yes, the living spec approach supports audit, proposal, and update workflows, allowing you to review and modify existing system requirements, domain models, and user stories as system behavior evolves.
Yes, you can use a living spec to document both current system behavior and intended future behavior, capturing domain models and requirements to align cross-functional teams on the product vision.
The best way to establish a shared vocabulary is to capture precise terminology definitions within a living spec, eliminating terminology drift and creating a single source of truth for all actors involved.
srobinsonCreates a structured SPEC.md template through interactive one-question-at-a-time elicitation.
JohannesKoningsValidate implementation plans against project domain models and documentation.
harshilLakhani22Define core objects, relationships, states, and vocabulary for a product conceptual model.
voidrotGenerate a Product Requirements Document from an epic with acceptance criteria.
