Skip to content

Add design-schematic interactive template#183

Merged
Alan-Jowett merged 3 commits intomicrosoft:mainfrom
Alan-Jowett:add-design-schematic-template
Apr 6, 2026
Merged

Add design-schematic interactive template#183
Alan-Jowett merged 3 commits intomicrosoft:mainfrom
Alan-Jowett:add-design-schematic-template

Conversation

@Alan-Jowett
Copy link
Copy Markdown
Member

Summary

Add a \design-schematic\ interactive template that guides users through complete schematic design — from requirements discovery through component selection to KiCad schematic output. This is Step 5 of 9 in the hardware design workflow, and the first template composing the new hardware protocols.

New Components

Type Name Path Description
Template (interactive) design-schematic templates/design-schematic.md End-to-end schematic design with component selection and audits

Also adds the \hardware-design\ template category in manifest.yaml.

Design Decisions

  • Composes 6 protocols: \component-selection, \component-selection-audit, \schematic-design, \schematic-compliance-audit, plus \�nti-hallucination\ and \self-verification\ guardrails. This is the first template to compose both generative and audit protocols in a single interactive session.
  • 8-phase workflow with human-in-the-loop gates: Requirements → Component Selection → Component Audit → User Review → Schematic Design → Schematic Audit → User Review → Deliver. Loop-back on REVISE at each gate.
  • Interactive mode: Follows the \interactive-design\ and \�ngineering-workflow\ patterns — no generation until user approves each phase.
  • New template category: \hardware-design\ in manifest, parallel to \code-analysis, \investigation, etc.
  • multi-artifact format: Produces KiCad files + BOM CSV + audit reports.

Checklist

  • All files have SPDX license headers
  • YAML frontmatter is valid and complete
  • Component names match file names (kebab-case)
  • manifest.yaml updated with new template and category
  • Template has input/output contracts
  • Template has a quality checklist section
  • Template references its persona, protocols, and format correctly
  • CI validation passes (\python tests/validate-manifest.py)

Add an interactive template that guides users through complete
schematic design — from requirements discovery through component
selection to KiCad schematic output. This is Step 5 of 9 in the
end-to-end hardware design workflow, and the first template in
the hardware-design category.

The template composes 6 protocols into an 8-phase workflow:
1. Requirements discovery (interactive)
2. Component selection (component-selection protocol)
3. Component selection audit (component-selection-audit protocol)
4. User review of components (gate — loop back if REVISE)
5. Schematic design (schematic-design protocol)
6. Schematic audit (schematic-compliance-audit protocol)
7. User review of schematic (gate — loop back to 2 or 5 if REVISE)
8. Deliver artifacts (KiCad files, BOM, reports)

Key design decisions:
- Interactive mode with human-in-the-loop review at every gate
- Composes both generative and audit protocols in a single session
  (generate -> audit -> user review -> proceed or loop back)
- Uses electrical-engineer persona (existing)
- multi-artifact format for KiCad files + BOM + reports
- Added new hardware-design template category in manifest
- Follows the interactive-design and engineering-workflow patterns

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings April 6, 2026 19:07
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new interactive PromptKit template for end-to-end hardware schematic design, and registers it in the library manifest under a new hardware-design template category.

Changes:

  • Introduces templates/design-schematic.md, an 8-phase interactive schematic design workflow composing hardware selection/design protocols plus audits.
  • Updates manifest.yaml to add a new hardware-design category and register the design-schematic template.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
templates/design-schematic.md New interactive template guiding requirements → component selection/audit → schematic design/audit → artifact delivery.
manifest.yaml Registers the new template under a new hardware-design category with the appropriate persona/protocols/format.

1. Changed CR-IDs to REQ-IDs with hardware category tag (REQ-HW-001)
   for consistency with PromptKit's universal REQ-ID convention used
   across all templates.

2. Phase 8 referenced design-pcb-layout, emit-manufacturing-artifacts,
   and hardware-design-workflow templates that don't exist yet.
   Genericized to describe the next steps without naming non-existent
   templates.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

1. Changed format from multi-artifact to null. Interactive templates
   should not declare a format that imposes output structure during
   Q&A phases (1-7). The engineering-workflow template uses the same
   pattern. Artifact structure is defined explicitly in Phase 8.

2. Schematic audit transition rules used 'Critical or High findings'
   but schematic-compliance-audit doesn't define severity levels.
   Replaced with explicit PASS/FAIL verdict consistent with
   component-selection-audit's verdict pattern.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

@Alan-Jowett Alan-Jowett merged commit 5f0d4d4 into microsoft:main Apr 6, 2026
7 checks passed
@Alan-Jowett Alan-Jowett deleted the add-design-schematic-template branch April 6, 2026 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants