write-tc

Name: write-tc
Availability: InStock
Author: MediSolveAIDev

Convert narrative scenarios into structured test-case JSON files.

Updated Feb 11, 2026

Search Tags:#qa #json #confluence #test-case #scenario-based #tc-writing

Ready to run

npx skills add https://github.com/MediSolveAIDev/QA-MEDI-PLUGIN --skill write-tc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-tc
Source: https://github.com/MediSolveAIDev/QA-MEDI-PLUGIN/tree/main/.claude/skills/write-tc
Command: npx skills add https://github.com/MediSolveAIDev/QA-MEDI-PLUGIN --skill write-tc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

시나리오를 바탕으로 테스트 케이스(TC)를 체계적으로 작성하는 데 필요한 수작업을 대폭 줄이고, 재현 가능한 JSON TC 스키마로 품질 검증을 용이하게 합니다.

Core Features & Use Cases

시나리오를 TC JSON으로 자동 변환
Confluence/Page ID, 또는 Figma 노드 ID를 참조하여 TC를 연결하고 관리
TC 스키마를 강제하여 메타데이터(depth_1~depth_6), 우선순위, 기대결과 등을 일관되게 유지

Quick Start

Provide a scenario narrative to generate a structured TC JSON file.

Frequently Asked Questions about write-tc

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

FAQPage Schema

How do I convert scenario narratives into structured test cases automatically?▼

Converting scenario narratives into structured test cases is done by transforming the text into a JSON TC schema with fields like id, priority, and expected results. You provide the scenario narrative, and the system generates the structured test-case JSON file automatically.

What is the JSON schema format for generating test cases from Confluence scenarios?▼

The test-case JSON schema enforces specific metadata fields including id, depth_1 through depth_6, priority, expected, and note. This structured format ensures consistent test case creation and preserves IDs during subsequent edits.

Can I link Confluence Page IDs or Figma node IDs to generated test cases?▼

Yes, you can reference Confluence Page IDs or Figma node IDs to connect and manage test cases. This anchors the generated TC JSON files to the original design specs and scenario sources for traceable QA workflows.

How do I maintain test case IDs when editing existing scenario-based JSON files?▼

Maintaining test case IDs during edits is handled natively by preserving the id field within the JSON TC schema. The system enforces this schema structure to ensure existing identifiers remain intact while updating other metadata fields like priority or expected results.

Does this test case generation approach work for QA planning across multiple design specs?▼

Test case generation applies to QA workflows across Confluence-based planning, design specs, and scenario sources. It systematically reduces manual effort by converting narrative scenarios from these various platforms into reproducible JSON test cases.

What's the best way to structure depth and priority in automated test case JSON?▼

Structuring depth and priority in test case JSON is enforced through the schema's depth_1 through depth_6 hierarchy and a dedicated priority field. The system automatically maps narrative scenarios to these layered metadata fields for consistent quality verification.