'traceability' 검색 결과

Verify that design documents, code implementations, and tests fully cover all specified requirements. Use this skill when validating requirement traceability, conducting design reviews, assessing implementation completeness, checking test coverage against requirements, performing compliance audits, or identifying missing functionality. Produces coverage reports showing which requirements are satisfied, partially satisfied, or missing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Inspect an unfamiliar repository, turn a focused Markdown behavior scenario into a deterministic test in the repository's native test stack, run it, and preserve traceability between intent and code. Use when asked to add scenario tests, compile acceptance criteria or Given/When/Then Markdown into executable tests, reproduce a user-visible regression, or convert a narrow workflow specification into stable web, API, CLI, desktop, or mobile interaction coverage. Do not use for broad exploratory journeys or agent-judged smoke tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Think and work like an expert Metrology Scientist. Use when a task calls for Metrology Scientist judgment. Reason from SI traceability, GUM uncertainty budgets, and VIM distinctions between calibration and verification; propagates Type A/B components, CIPM MRA equivalence, and ILAC decision rules before any pass/fail claim.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Think and work like an expert Clinical Data Manager. Use when a task calls for Clinical Data Manager judgment. Reasons from ALCOA+ data integrity, traceability, and analysis-ready datasets through CDASH/SDTM/ADaM pipelines, edit-check specs, Pinnacle 21 validation, MedDRA/WHO Drug coding, and define.xml under 21 CFR Part 11, treating blinding breaches, SAE-safety reconciliation gaps, mid-study IG/dictionary version drift, and unspecified partial-date imputation as first-class failure modes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Think and work like an expert Analytical Chemist. Use when a task calls for Analytical Chemist judgment. Reasons from the chemical measurement process through ICH Q2(R2) and USP <621> validation, CRM traceability, EURACHEM uncertainty budgets, and HPLC/GC/LC-MS/ICP-MS workflows while treating matrix effects, SST drift, peak tailing, and ion suppression as first-class failure modes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reads, validates, and prepares CDISC SDTM and ADaM clinical trial data for analysis. Covers SDTM domain joins (DM, AE, EX, VS, LB, DS), ADaM architecture (ADSL, BDS, OCCDS, ADTTE) with traceability, treatment-emergent AE conventions, baseline derivation, SUPPQUAL/NSV handling, Define-XML 2.1, and Pinnacle 21 / CORE validation. Use when working with clinical trial datasets in CDISC SDTM/ADaM format, preparing analysis-ready data, or validating for regulatory submission.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Extracts and records architectural decisions from diffs, conversation context, and explicit choices. Supports automatic extraction from staged changes, deduplication against prior decisions, and persistent ADR-format logging with spec traceability. Use after a significant design or architecture choice, before committing a diff that embeds implicit decisions, or when the same question keeps resurfacing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Use before claiming code is complete.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests. Use after happy-path tests exist and before claiming coverage is complete, when requirements lack tests, or before a security review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When a GDD is revised, scans all ADRs and the traceability index to identify which architectural decisions are now potentially stale. Produces a change impact report and guides the user through resolution.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Authoring standalone and cross-team specifications: PRD/SRS/HLD/LLD, staged L0-L4 unified packages, BDD acceptance criteria, and traceability. Use for technical or multi-audience documentation; not implementation or architecture decisions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Verifying spec compliance: extracts ACs from specs, adversarially checks conformance, generates BDD scenarios and traceability matrices. Use when impl must be proven to match a PRD/SRS/AC.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Systems engineering covering requirements management, the V-model lifecycle, integration planning, verification and validation (V&V), interface control, trade studies, and the NASA Systems Engineering Handbook. Spans the full lifecycle from concept through operations and disposal. Includes requirements decomposition, traceability matrices, configuration management, and technical performance measures. Use when managing complex system development, writing requirements, planning integration, or conducting V&V activities.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Git-as-knowledge-graph workflow for traceability. Use when planning work, brainstorming designs, creating/managing issues and PRs, tracking architectural decisions, or resuming prior sessions. Slash command /shiplog.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Central dispatcher for the canvas/state render fleet. Routes intent to a specialist (`/mycelium:diamond-render`, `/mycelium:ost-render`, `/mycelium:cycle-render`) OR lists what's renderable. Cross-cutting views spanning multiple canvases (opp→sol→cycle traceability, confidence-over-time, cluster-graduation-flow) are research-gated and NOT emitted by default. See `${CLAUDE_PLUGIN_ROOT}/engine/render-conventions.md` for shared conventions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design a compliance architecture that maps applicable regulations to computerized systems. Covers system inventory, criticality classification (GxP-critical, GxP-supporting, non-GxP), GAMP 5 category assignment, regulatory requirements traceability, and governance structure definition. Use when establishing a new regulated facility, formalising compliance across multiple systems, addressing a regulatory gap analysis, harmonising compliance after mergers or reorganisations, or preparing a site master file that references computerized systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Transform Markdown or text specifications into human-readable HTML documents with summaries, reordered structure, visual explanations, diagrams, charts, and traceability to the source. Use when asked to convert a spec, requirements document, API spec, product spec, design doc, or technical document into readable HTML, especially when the user wants summarization, restructuring, diagrams, graphs, images, or visual aids rather than a literal Markdown-to-HTML conversion.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Display the current VCSDD pipeline status for the active (or specified) feature. Shows phase, mode, sprint count, open findings, pending proofs, and the traceability summary.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Display the full traceability chain for a VCSDD bead. Traverses the Chainlink graph from the given bead ID and shows all connected artifacts with status.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fix bugs and technical debt with minimal ceremony. Issue GitHub optional — provide one for traceability or work free-form. Replaces /issue-fix.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a task needs the judgment of a biomedical/bioengineering engineer — running a design control phase (inputs, outputs, verification, validation) for a medical device, scoring a Design FMEA and deciding whether a failure mode needs mitigation, planning a human factors/usability validation study, building a design traceability matrix, or writing a design verification or risk-mitigation report. Distinct from a regulatory-affairs-specialist (owns the submission/clearance process, not the engineering itself) and from a clinical-data-manager/biostatistician (trial data and analysis, not device design).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a task needs the judgment of an Agricultural Inspector — grading a lot of produce against a USDA grade standard's defect tolerances, evaluating agricultural water test results against FSMA microbial thresholds, checking a pesticide residue result against the commodity-specific EPA tolerance, deciding whether a finding warrants a stop-sale order versus a corrective-action letter, or verifying a facility's traceability records against a recall deadline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.