harness-design-review

Creates pre-implementation design review documents for MIL-STD-1553B harness engineering tasks.

Updated Nov 22, 2023
One-click install
npx skills add https://github.com/parksanghoon-sys/TestCode --skill harness-design-review-parksanghoon-sys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-design-review
Source: https://github.com/parksanghoon-sys/TestCode/tree/main/src/MIL-STD-1553B/.agents/skills/harness-design-review
Command: npx skills add https://github.com/parksanghoon-sys/TestCode --skill harness-design-review-parksanghoon-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? When new features, bug fixes, protocol changes, device integrations, or test harness modifications are requested in a MIL-STD-1553B project, jumping straight into code leads to unclear responsibilities and missed requirements. This Skill enforces a mandatory design review step before any implementation begins. ## Core Features & Use Cases - Structured Design Review Documents: Generates Korean-language design review documents covering background, scope, requirements, C++/C# responsibility separation, clean architecture layer impact, object/interface drafts, TDD plans, risks, and completion criteria. - MIL-STD-1553B Impact Analysis: Systematically reviews BC/RT/BM impact, Command/Status/Data Words, Mode Codes, Bus A/B switching, error injection, and timeout requirements. - Template-Based Output: Writes documents to docs/design/YYYY-MM-DD_기능명_설계검토.md following the provided template in assets/. - Use Case: When asked to add a new RT simulation feature, use this Skill first to produce a design review document defining the C++ simulator core changes, C# scenario control changes, and the TDD Red test plan before writing any production code. ## Quick Start Before implementing the new Mode Code handling feature, create a design review document analyzing the BC/RT impact and C++/C# responsibility split.

Frequently Asked Questions about harness-design-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a design review document before implementing a MIL-STD-1553B feature?▼

Invoke this Skill before writing any code when a feature, bug fix, or protocol change is requested. It guides you through requirements, scope, C++/C# responsibility separation, and TDD planning, then writes the document to docs/design/ following the provided template.

What should a MIL-STD-1553B design review document include?▼

It should cover BC/RT/BM impact, Command/Status/Data Words, Mode Codes, Bus A/B switching, timeout and error injection handling, clean architecture layer impact, class and interface drafts, data flow, test strategy, risks, and completion criteria.

When should I not use a design review step?▼

Skip this Skill when the task is to write code directly without a preceding design phase. It is strictly for pre-implementation review and explicitly prohibits writing production code during the design stage.

How are C++ and C# responsibilities separated in a 1553B harness?▼

C++ handles device SDK integration, word/message parsing, frame assembly, simulator core, and high-performance timing. C# handles scenario control, operator UI/CLI, configuration editing, report display, test orchestration, and log aggregation.

Where are the generated design review documents stored?▼

Documents are written to the docs/design/ directory with the naming pattern YYYY-MM-DD_feature-name_design-review.md, following the structure of the template file in the assets directory.