Advance engineering phases from design documents through gate-based PR progression.
npx skills add https://github.com/noho/code-is-cheap --skill phaseflow
Please help me install this Agent Skill. Skill: phaseflow Source: https://github.com/noho/code-is-cheap/tree/main/skills/phaseflow Command: npx skills add https://github.com/noho/code-is-cheap --skill phaseflow
phaseflow helps you move a complex engineering phase forward in a controlled engineering loop by using a design source as the decision truth and a control document as the execution and gatekeeping truth.
design_doc as the primary authority for phase design, planning, and review judgments to ensure outcomes match the intended architecture and success criteria.control_doc: Reads and continuously updates the phase state, work-unit status, artifact paths, commit hashes, review conclusions, residual risks, and next entry points.ready-to-open-draft-PR, then (after user authorization) continues through the draft PR gate until draft-PR-pass.Run phaseflow with your design document and implementation control document so it can read control_doc first, then plan and route work to move the current phase to the draft PR gate.
High-intent search queries and answers about installing and using this skill.
Drive phase development from design to draft PR by ingesting a control document for execution truth and a design document for decision truth, then routing work through specialist agents and gate-based progression until the draft PR passes.
Design-driven phase control uses a design document as the primary authority for planning and review judgments, ensuring feature execution outcomes match the intended architecture and success criteria.
Track residual risks and review adjudication by continuously updating a control document with work-unit status, review conclusions, and durable accept, reject, or defer findings throughout the refactor phase.
Yes, agent orchestration dispatches specialist agents for implementation and consolidates independent reviews to govern migration PR gates from phase discussion through ready-to-open-draft-PR to draft-PR-pass.
Yes, a control document is required as the execution and gatekeeping truth to enforce phase boundaries, track entry and exit criteria, and record commit hashes and next entry points.
Gate-based phase progression should be avoided when phase boundaries, explicit entry and exit criteria, and residual risk tracking are not required for the engineering task.
qvidal01Sequence ideation artifacts into phased roadmaps with falsifiable exit criteria.
jpeggdevManage draft status of stacked GitHub Pull Requests.
harkersReview bounded work for correctness and output evidence-linked findings with a disposition.
ajsai47Dispatches a dedicated reviewer to inspect code changes and categorize severity of defects.