Close a CR after a PASS post-build review with human confirmation.
npx skills add https://github.com/Angel1104/praxis-core --skill ship-angel1104
Please help me install this Agent Skill. Skill: ship Source: https://github.com/Angel1104/praxis-core/tree/main/skills/ship Command: npx skills add https://github.com/Angel1104/praxis-core --skill ship-angel1104
Formal CR closure after post-build review, ensuring human confirmation and traceable outcomes.
Run the ship command with the CR-ID after a PASS in /audit to finalize closure.
High-intent search queries and answers about installing and using this skill.
To close a CR after post-build review, run the ship command with the CR-ID after a PASS verdict in /audit. The system verifies acceptance criteria and generates a closure artifact for human confirmation.
Formal CR closure and traceability is the process of finalizing a Change Request after post-build review, generating a closure artifact, documenting lessons learned, and updating backlog status to ensure human confirmation and traceable outcomes.
You need a closure artifact for a Change Request when a post-build review has produced a PASS verdict and you are ready to finalize the CR. The system generates this artifact to document the outcome and capture lessons learned.
Yes, CR closure requires human confirmation before finalizing. The system surfaces any blockers or missing artifacts for human decision and waits for explicit confirmation before closing the CR and updating the backlog.
If there are blockers or missing artifacts during CR closure, the system surfaces them for human decision. It prevents automatic closure and ensures that any missing artifacts are resolved before the CR is finalized.
Yes, you can create follow-up CRs during the closure process. When closing a CR, the system documents lessons learned and automatically creates follow-up CRs if needed to ensure traceable outcomes and continuous improvement.
LeoCode03Automates post-build review to produce a PASS or BLOCKED verdict.
Angel1104Automate change request closure after successful builds with a Phase 1-5 workflow.
LeoCode03Generates CR specification documents with domain, architecture, security analysis.
terrazul-aiGenerate draft responses for batches of open tickets using templates.
