Generate a spec and plan document from sphinx-needs requirements.
npx skills add https://github.com/useblocks/pharaoh --skill pharaoh-spec
Please help me install this Agent Skill. Skill: pharaoh-spec Source: https://github.com/useblocks/pharaoh/tree/main/skills/pharaoh-spec Command: npx skills add https://github.com/useblocks/pharaoh --skill pharaoh-spec
Generate a self-contained specification and plan document from one or more sphinx-needs requirements, bridging the gap between what needs to implement and how to implement it. It maps downstream coverage, identifies gaps, records design decisions via pharaoh:decide, and outputs a plan-ready document that feeds into pharaoh:plan.
Provide one or more sphinx-needs requirement IDs to generate a combined spec and plan document ready for review.
High-intent search queries and answers about installing and using this skill.
You can generate a combined spec and plan document by providing one or more sphinx-needs requirement IDs, which pulls full requirement text, identifies coverage gaps, records design decisions, and outputs a plan-ready document.
Requirements traceability tracks downstream coverage from root needs to implementation, identifying gaps and recording design decisions to produce a plan-ready document ensuring end-to-end alignment between specifications and execution.
Identifying gaps in downstream coverage involves mapping your sphinx-needs requirements against existing implementations, highlighting missing areas, and recording design decisions to ensure full traceability before generating a plan.
Yes, you can record design decisions alongside requirement specifications using the pharaoh:decide mechanism, ensuring every gap and coverage choice is documented for full traceability within the generated plan document.
Yes, it works directly with sphinx-needs by pulling full requirement text for root needs and producing a plan table that maps downstream coverage, which can then be executed by pharaoh:plan.
The main limitation is that generating a combined spec and plan document requires existing sphinx-needs requirement IDs as input; without properly defined root needs, the downstream coverage mapping and plan generation cannot function.
patdhlkAutomate MECE-based analysis of sphinx-needs requirement graphs for gaps and redundancies.
Prat011Convert Notion specs into implementation plans with tasks and milestones.
useblocksRecord design decisions as sphinx-needs directives with decided_by, alternatives, and rationale.
tractorjuiceGenerate requirements traceability matrices linking design, implementation, and test artifacts.
