Record design decisions as sphinx-needs directives with decided_by, alternatives, and rationale.
npx skills add https://github.com/useblocks/pharaoh --skill pharaoh-decide
Please help me install this Agent Skill. Skill: pharaoh-decide Source: https://github.com/useblocks/pharaoh/tree/main/skills/pharaoh-decide Command: npx skills add https://github.com/useblocks/pharaoh --skill pharaoh-decide
Record design decisions as traceable sphinx-needs decision directives. Each decision captures the chosen option, rejected alternatives, rationale, and explicit links to the requirements or specifications it affects.
Draft and store a new decision with a title, affected needs, decided_by, alternatives, and rationale to create a new decision entry.
High-intent search queries and answers about installing and using this skill.
To record design decisions with traceability, you create sphinx-needs decision directives that capture the chosen option, rejected alternatives, and rationale, while explicitly linking to affected requirements or specifications to maintain a coherent decision history.
Documenting rejected alternatives and rationale in Sphinx requires creating decision directives that provide dedicated fields for alternatives and rationale, ensuring design outcomes and the reasoning behind them are fully codified for auditability.
Linking design decisions to affected needs or specifications for auditability involves applying decision directives that establish explicit connections to those requirements, capturing who made the decision in the decided_by field to support full traceability.
Yes, you can use sphinx-needs to track who made a design decision and why by utilizing the decided_by field to record the decision maker and the rationale field to document the reasoning, supporting complete auditability.
You need explicit decision directives for project documentation when your project requires full traceability and auditability, ensuring that chosen options, rejected alternatives, and rationale are explicitly linked to affected needs and specifications.
Yes, pharaoh-decide works with sphinx-needs workflows by allowing you to draft and store decision entries that codify design outcomes, capturing the chosen option, alternatives, and rationale directly within pharaoh-driven workflows.
patdhlkCreate or update sphinx-needs directives with schema-validated IDs, types, and links.
I2olanDTransform vague requirements into clear, testable specifications using elicitation techniques and documentation templates.
abhishekdutta18Analyze revenue, refunds, and billing behavior against implementation code.
useblocksGenerate a spec and plan document from sphinx-needs requirements.
