Add hardware-design-workflow orchestrating template#193
Merged
Alan-Jowett merged 3 commits intomicrosoft:mainfrom Apr 6, 2026
Merged
Add hardware-design-workflow orchestrating template#193Alan-Jowett merged 3 commits intomicrosoft:mainfrom
Alan-Jowett merged 3 commits intomicrosoft:mainfrom
Conversation
Add the end-to-end hardware design workflow template that orchestrates all hardware protocols into a single interactive session. This is Step 8 of 9 in the hardware design workflow. The template composes 10 protocols into a 9-phase workflow: 1. Requirements discovery (requirements-elicitation) 2. Component selection (component-selection) 3. Component audit + user review (component-selection-audit) 4. Schematic design (schematic-design) 5. Schematic audit + user review (schematic-compliance-audit) 6. PCB layout & routing (pcb-layout-design) 7. Layout audit + user review (layout-design-review) 8. Manufacturing artifacts (manufacturing-artifact-generation) 9. Pre-submission review + delivery Each phase has explicit transition rules with loop-back support: - Phase 3 -> Phase 2 (revise components) - Phase 5 -> Phase 4 or 2 (revise schematic or components) - Phase 7 -> Phase 6, 4, or 2 (revise layout, schematic, or components — handles the schematic-layout feedback loop) - Phase 9 -> any earlier phase if issues found Also updates applicable_to on all 8 hardware protocols to include hardware-design-workflow (and design-schematic where applicable). Removes standalone composition notes from protocols that now have template references. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new interactive orchestration template that composes the existing hardware design protocols into a single end-to-end workflow (requirements → components → schematic → PCB layout → manufacturing deliverables), and updates protocol metadata/manifest entries to reflect the new composition.
Changes:
- Added
hardware-design-workflowinteractive template that sequences 9 phases with audit + user gates. - Updated
applicable_tometadata on several hardware-related protocols to includehardware-design-workflow(anddesign-schematicwhere appropriate) and removed now-stale “composition note” text. - Registered the new template in
manifest.yamlunder thehardware-designcategory with the composed protocol list.
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| templates/hardware-design-workflow.md | New capstone interactive template orchestrating the full hardware workflow across requirements, design, audit, layout, and manufacturing phases. |
| protocols/reasoning/component-selection.md | Marks the protocol as required by design-schematic and hardware-design-workflow; removes standalone composition note. |
| protocols/analysis/component-selection-audit.md | Marks the protocol as required by design-schematic and hardware-design-workflow; removes standalone composition note. |
| protocols/reasoning/schematic-design.md | Marks the protocol as required by design-schematic and hardware-design-workflow; removes standalone composition note. |
| protocols/analysis/schematic-compliance-audit.md | Adds design-schematic and hardware-design-workflow to applicable_to. |
| protocols/reasoning/pcb-layout-design.md | Adds hardware-design-workflow to applicable_to. |
| protocols/analysis/layout-design-review.md | Adds hardware-design-workflow to applicable_to. |
| protocols/reasoning/manufacturing-artifact-generation.md | Adds hardware-design-workflow to applicable_to. |
| manifest.yaml | Adds the new template entry and its composed protocol list under hardware-design. |
1. requirements-elicitation protocol applicable_to was missing hardware-design-workflow. Added per CONTRIBUTING.md convention. 2. YAML folded block split 'pick-and-place' across lines producing 'pick-and- place' when parsed. Rewrapped to keep compound word intact. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Phase 1 output used 'Must/Should/May' but the composed requirements-elicitation protocol uses RFC 2119 keywords (MUST/SHOULD/MAY) and requires acceptance criteria. Both instructions would be active in the assembled prompt, creating a conflict. Aligned to RFC 2119 and added acceptance criteria. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add the \hardware-design-workflow\ template — the end-to-end orchestrator that guides users from initial idea to manufacturable PCB artifacts. This is Step 8 of 9, and the capstone of the hardware design workflow.
New Components
Changes to Existing Components
Updated \�pplicable_to\ on all 8 hardware protocols to include \hardware-design-workflow\ (and \design-schematic\ where applicable). Removed standalone composition notes from protocols that now have template references.
Design Decisions
Checklist