Guide conversations to capture system specifications and domain models.
npx skills add https://github.com/wrteam-jay/blueprint --skill elicit-wrteam-jay
Please help me install this Agent Skill. Skill: elicit Source: https://github.com/wrteam-jay/blueprint/tree/main/skills/blueprint/skills/elicit Command: npx skills add https://github.com/wrteam-jay/blueprint --skill elicit-wrteam-jay
This Skill addresses the friction caused by tribal knowledge, terminology drift, lack of a shared reference, and the gap between a system's intent and its reality. It helps create a single source of truth for how a system works.
Use the elicit skill to start building a blueprint from scratch by describing the system's purpose.
High-intent search queries and answers about installing and using this skill.
The elicitation process facilitates creating living system specifications by guiding users through a conversation to capture context, actors, and requirements. It eliminates tribal knowledge and terminology drift by establishing a shared reference for system behavior and intent.
The best way to document user stories and domain models is through a conversational elicitation process that builds a living blueprint. This method establishes a shared vocabulary and traces end-to-end scenarios to ensure a shared understanding before development begins.
Yes, you can map out both happy paths and failure conditions by tracing end-to-end scenarios during the specification process. This flow mapping captures the complete user journey from initiation to completion, ensuring all edge cases are documented.
No, building a system blueprint explicitly enforces constraints prohibiting any implementation details. The specification focuses entirely on system behavior and intent, ensuring the document remains a pure representation of requirements rather than technical execution.
You ensure shared understanding by using the skill to establish and define a shared vocabulary for your system during the specification process. This addresses terminology drift by defining terms like user, order, and payment within a single source of truth.
coreyhaines31Your SaaS company
sirius-cc-wuTransform vague ideas into formal software specification documents.
nextbysamArchive completed change proposals and merge specification deltas into living documentation.
spqwProvides DOM event, timer, and MQTT generators for Blazor hybrid apps.
