Plan requirement changes into ordered executable tasks with skill mappings.
npx skills add https://github.com/useblocks/pharaoh --skill pharaoh-plan-useblocks
Please help me install this Agent Skill. Skill: pharaoh-plan Source: https://github.com/useblocks/pharaoh/tree/main/skills/pharaoh-plan Command: npx skills add https://github.com/useblocks/pharaoh --skill pharaoh-plan-useblocks
Breaks down large requirement changes into a structured, executable plan that can be enacted with Pharaoh skills while respecting workflow gates and traceability across the project.
Plan and generate an ordered set of tasks describing which skill to invoke for each target artefact and its associated file.
High-intent search queries and answers about installing and using this skill.
To break requirement changes into an executable plan, map changes to top-level needs and downstream artefacts to enforce ordering across requirements, specifications, implementations, and tests, generating a concrete task list with exact skills and target files for execution.
Traceability in change management planning ensures workflow gates are enforced by mapping requirement changes to top-level needs, specifications, implementations, and tests, minimizing rework and maintaining end-to-end order across the project lifecycle.
Enforce workflow gates across needs, specifications, and tests by orchestrating end-to-end planning that applies ordering constraints to requirement changes, generating a step-by-step execution plan enacted by designated skills for each target artefact.
Yes, you can map requirement changes to specific target artefacts and skills by generating a concrete task list that defines exact skill mappings and associated files, ensuring each step is executable and traceable within the workflow.
The best way to minimize rework when planning requirement changes is to enforce strict ordering across requirements, specifications, implementations, and tests, ensuring downstream artefacts are only generated after upstream workflow gates are satisfied.
Yes, you need existing requirement changes to generate a step-by-step execution plan, as the planning process defines required inputs and constraints to break those changes into an ordered task list with exact skills for target artefacts.
MoaidHathotDefine and validate Orchestra orchestrations in YAML/JSON.
BlackBeltTechnologyVerify code implementations against specifications, tasks, and design documents.
rockandrolla13Create, update, and verify PLAN-*.md files for multi-step workflows.
cshyangGroup requirements into phases and generate a validated roadmap with traceability.
