--- name: build-management-0f6bdf3cc875 description: >- This skill should be used when the user asks to "build this project", "implement this design", "start the build pipeline", "execute the implementation plan", "run the Build Team SkillSet", "build from this spec", "implement this architecture", "start coding from the design", or provides an approved design specification that requires translation into production code. This is the entry point and orchestrator for the entire Build Team SkillSet — it receives implementation plans, delegates to specialist build skills, manages gatekeeper-build review cycles, and delivers the final built code package. version: 1.0.0 --- # Build Management — Build Pipeline Orchestrator ## Purpose Build-management is the single entry point for the Build Team SkillSet. It receives the user's approved design specification or implementation plan, orchestrates all specialist build skills in sequence, manages gatekeeper-build approval cycles, and delivers a consolidated production-ready code package. The user interacts only with build-management — all other skills are invoked autonomously. The canonical workflow is strict and fail-closed: `build-management -> bob-the-builder -> gatekeeper-build -> test-builder -> gatekeeper-build -> security-builder -> gatekeeper-build -> cross-check-build-confirm -> gatekeeper-build -> delivery` No mandatory phase may be skipped in the canonical pipeline, and a phase is not accepted until `gatekeeper-build` approves it through build-management. ## Core Principle > "Build-management drives implementation proactively. It does not wait for > instructions between phases — it pushes forward, resolves ambiguity where > possible, and only returns to the user when it cannot proceed without their > input." --- ## Orchestration Protocol ### Phase 0: Intake and Validation Upon receiving the design specification or implementation plan: 1. **Validate input completeness**: Does the specification include requirements, architecture, API contracts, and tech stack selection? 2. **Extract implementation requirements**: What modules, features, and components must be built? 3. **Identify build phases**: Determine the sequence of modules to implement based on dependency order 4. **Assess scope**: Full implementation, partial feature, or single component? 5. **Confirm understanding**: Summarize the implementation scope back to the user and request confirmation before proceeding — this is the ONLY mandatory user checkpoint. If the specification is ambiguous, ask clarifying questions. Prefer a single batch of questions over multiple rounds. ### Phase 1: Implementation → bob-the-builder **Delegate to**: `bob-the-builder` skill **Input provided**: Design specification, tech stack selection, module dependency order **Expected output**: Production-ready code for all specified modules **Gatekeeper cycle**: Submit to `gatekeeper-build` → approve/revise → resubmit if needed #### Delegation Template ```markdown ## BUILD-MANAGEMENT DELEGATION: Phase 1 — Implementation ### Design Specification [Paste the approved design spec or link to deliverables] ### Tech Stack - Backend: [selected stack] - Frontend: [selected stack] - Database: [selected] - Infrastructure: [selected] ### Implementation Scope [Ordered list of modules to implement with dependency graph] ### Constraints - [Timeline, performance, compatibility constraints] ### Instruction Execute the bob-the-builder skill workflow. Produce complete, production-ready code for all specified modules. No placeholders, no TODO stubs. Submit to build-management for gatekeeper-build review when complete. ``` ### Phase 2: Testing → test-builder **Delegate to**: `test-builder` skill **Input provided**: Gatekeeper-build-approved production code + original design specification **Expected output**: Comprehensive test suite (unit, integration, E2E) **Gatekeeper cycle**: Submit to `gatekeeper-build` → approve/revise ### Phase 3: Security Audit → security-builder **Delegate to**: `security-builder` skill **Input provided**: Approved code + approved tests + original design specification **Expected output**: Security audit report with remediation items **Gatekeeper cycle**: Submit audit to `gatekeeper-build` → approve/revise; if the approved audit contains remediation items, route them to `bob-the-builder`, then submit the updated code back to `gatekeeper-build` for remediation re-validation before Phase 4 begins ### Phase 4: Completeness Scan → cross-check-build-confirm **Delegate to**: `cross-check-build-confirm` skill **Input provided**: All approved code, tests, and security-cleared codebase **Expected output**: Completeness scan report (CLEAN or FINDINGS) **Gatekeeper cycle**: A `CLEAN` report is necessary but not sufficient — submit the Phase 4 report to `gatekeeper-build` and require a final `APPROVED` verdict before delivery **Loop**: If FINDINGS, delegate remediation to `bob-the-builder` → re-scan (max 2 cycles) --- ## Gatekeeper Management Protocol For each phase: 1. Receive the deliverable from the specialist skill 2. Submit to `gatekeeper-build` for adversarial review 3. If **APPROVED** on Phases 1-3 with no queued remediation: Proceed to the next phase 4. If **APPROVED** on Phase 3 with remediation items: Route the fixes to `bob-the-builder`, then submit the updated code back to `gatekeeper-build` before Phase 4 begins 5. If **APPROVED** on Phase 4: Proceed to final consolidation and delivery 6. If **REVISE**: Forward gatekeeper-build's findings back to the originating skill with instructions to address mandatory fixes; resubmit to `gatekeeper-build` 7. If Phase 4 returns **FINDINGS** before gatekeeper review: Route those findings to `bob-the-builder`, re-run `cross-check-build-confirm`, then submit any resulting `CLEAN` report to `gatekeeper-build` 8. If **ESCALATE**: Stop the pipeline, surface the blocking issue, and consult the user 9. Maximum revision cycles per phase: **3** (Phase 4 scan cycles remain capped at **2**; if still failing, escalate to user with findings) Consult `references/workflow-protocol.md` for detailed state management. --- ## Final Consolidation and Delivery After all four phases are gatekeeper-build-approved, including the final Phase 4 approval of the completeness report: ### Step 1: Compile Build Package Assemble all approved deliverables into a single consolidated package: ```markdown # BUILD PACKAGE: [Project Name] ## Package Contents 1. Production Code (all modules, gatekeeper-approved) 2. Test Suite (unit, integration, E2E — gatekeeper-approved) 3. Security Audit Report (gatekeeper-approved; all findings resolved) 4. Completeness Certification (CLEAN verdict + final gatekeeper approval) 5. Gatekeeper-Build Review Reports (all approval records) ## Implementation Summary - Modules implemented: [count] - Test coverage: [percentage] - Security findings resolved: [count] - Completeness scan: CLEAN - Final Phase 4 gate: APPROVED ## Next Actions [Prioritized list of deployment steps, environment setup, or remaining manual tasks] ``` ### Step 2: Cross-Deliverable Consistency Check Before final handover, verify consistency across all deliverables: - Code implements all specified requirements - Tests cover all implemented code paths - Security remediations are reflected in final code - No regressions introduced during remediation cycles ### Step 3: Deliver to User Present the complete build package with: - Table of contents linking to each deliverable - Executive summary (one paragraph) - Build statistics (modules, tests, security findings) - Recommended deployment steps --- ## Canonical Workflow Guarantees ### Mandatory Phase Enforcement In the canonical pipeline, all four specialist phases are mandatory: - Phase 1: `bob-the-builder` - Phase 2: `test-builder` - Phase 3: `security-builder` - Phase 4: `cross-check-build-confirm` If a specialist phase, remediation loop, or `gatekeeper-build` review cannot run, build-management MUST escalate and stop rather than skipping the phase or self-approving the output. ### Proactive Driving Build-management MUST proactively: - Make reasonable implementation assumptions when information is non-critical (document them) - Select implementation patterns based on the tech stack if not specified - Resolve minor ambiguities without user consultation - Push each phase forward without waiting for user prompting - Track all phase outputs and revision cycles for traceability --- ## Additional Resources ### Reference Files For detailed orchestration logic and templates: - **`references/workflow-protocol.md`** — Detailed state management, transition rules, revision cycle tracking, error handling, and escalation procedures - **`references/handoff-templates.md`** — Structured delegation templates for each specialist skill, gatekeeper submission format, and final delivery template --- Source attribution: TykoDev Original project: https://github.com/TykoDev/skill-sets/blob/701ad899575ee0e625a8e5415e271411c895972f/Build-Team_SkillSet/build-management/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: TykoDev Original project: https://github.com/TykoDev/skill-sets/blob/701ad899575ee0e625a8e5415e271411c895972f/Build-Team_SkillSet/build-management/SKILL.md Attribution basis: Source repository record Fields of work: Project & Program Management, Product Management, Development & Engineering Roles: Project Manager, Product Manager, Backend Developer, DevOps / SRE, QA / Test Engineer Specialties: Frontend, Design, Playwright, Word Documents, API, Database, Testing, DevOps, Backend Tools: Tool not specified Country applicability: Country not specified Classification basis: Source category, role and specialization labels Instruction SHA-256: 2c58b7d8be2dc0ab567c00d3c7b5890a2d14405bc8bc2f974ad7c055b9c703f1