Automate change request closure after successful builds with a Phase 1-5 workflow.
npx skills add https://github.com/Angel1104/architecture-docs --skill close-angel1104
Please help me install this Agent Skill. Skill: close Source: https://github.com/Angel1104/architecture-docs/tree/main/FE-MOBILE/commands/close Command: npx skills add https://github.com/Angel1104/architecture-docs --skill close-angel1104
Manual CR closure is error-prone and time-consuming. This skill automates the formal closure process after a build by validating acceptance criteria, documenting outcomes, surfacing lessons learned, and proposing follow-ups.
Close a CR by running the closure workflow after build approval and providing the CR-ID to finalize the closure and update the CR item.
High-intent search queries and answers about installing and using this skill.
Automate change request closure by running a structured Phase 1-5 workflow that validates acceptance criteria against build results, drafts closure summaries, and updates project specs. This enforces governance by requiring intake data and tool access to run tests before finalizing.
The formal CR closure workflow is a mandated Phase 1-5 process that verifies acceptance criteria, documents outcomes, and surfaces lessons learned. It requires accessing build results and intake specifications to analyze test results and confirm the original intent.
Flag follow-up work during the CR closure process by analyzing build results and intake data to identify lessons learned. The workflow automatically proposes follow-up CRs or improvements and appends these outcomes to the CR item history.
Yes, finalizing CR closure requires access to build results, intake data, project specs, and tooling to run tests. These inputs are strictly necessary to verify acceptance criteria and automatically update the CR item and specs.
Yes, you can update project specs and CR history automatically by executing the closure workflow after build approval. Providing the CR-ID triggers the process to append summaries and finalize the documentation.
The best way to enforce governance for CR closure is applying an automated Phase 1-5 workflow that mandates verification of acceptance criteria and documentation of outcomes. This prevents manual errors by requiring build results and intake access before closure.
Busboom-FooAssess code changes against acceptance criteria with a two-phase review workflow.
KirKruglovGenerate project closure reports from charter, plan-fact, risk register, and lessons.
Angel1104Close a CR after a PASS post-build review with human confirmation.
Lands-1203Generate project architecture description drafts from documentation or code.
