skills.rest
tsuji-tomonori
tsuji-tomonoriCOMMUNITY
Explore all skills by this author →
GitHub

doc-at-scn

Generate and revise AT-SCN Markdown documents with required frontmatter and judgment criteria.

1|Updated Feb 11, 2026
Search Tags:#testing#documentation#markdown#acceptance criteria#obsidian#at-scn
One-click install
npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-at-scn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-at-scn
Source: https://github.com/tsuji-tomonori/diopside-v3/tree/main/.opencode/skills/doc-at-scn
Command: npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-at-scn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you create and revise Acceptance Test Scenario (AT-SCN) documents according to the diopside documentation standards, ensuring clarity and consistency in your testing procedures.

Core Features & Use Cases

  • New Document Creation: Generate new AT-SCN documents with all required frontmatter and sections.
  • Document Revision: Update existing AT-SCN documents to reflect changes in requirements, specifications, or acceptance criteria.
  • Use Case: When a new feature is implemented, use this Skill to draft the corresponding AT-SCN document, detailing the steps, expected results, and judgment criteria for verifying the feature's acceptance.

Quick Start

Use the doc-at-scn skill to create a new AT-SCN document for the feature ID 'FR-001'.

Frequently Asked Questions about doc-at-scn

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

FAQPage Schema
How do I write acceptance test scenarios in Markdown for Obsidian?▼

You can generate acceptance test scenario documents in Markdown format with mandatory frontmatter, structured scenarios, expected results, and judgment criteria to ensure verifiable acceptance testing.

What is an AT-SCN document and when do I need one?▼

An AT-SCN document defines acceptance test scenarios, expected results, and judgment criteria. You need one when implementing a new feature to verify its acceptance through clear, structured testing procedures.

Can I update existing acceptance criteria documents when requirements change?▼

Yes, you can revise existing AT-SCN documents to reflect changes in requirements, specifications, or acceptance criteria while maintaining consistent frontmatter and Obsidian operational standards.

Does this approach require specific frontmatter for Obsidian documentation standards?▼

Yes, generating AT-SCN documents requires mandatory frontmatter and structured content sections to adhere to diopside's Obsidian operational standards for clear and verifiable acceptance testing.

What's the best way to structure expected results and judgment criteria in testing documentation?▼

Structure them within dedicated sections of the AT-SCN Markdown document, ensuring each scenario details the steps, expected results, and judgment criteria needed to verify feature acceptance.

Why does my acceptance test scenario need judgment criteria?▼

Judgment criteria are required in AT-SCN documents to facilitate clear and verifiable acceptance testing, ensuring that each scenario's expected results can be objectively evaluated.

Related Skills

Explore More Software Engineering Skills→
ZTE-AICloudZTE-AICloud
52

reverse-requirements

Extract EARS-style requirements from SCN-*.md scene documents.

Official
Advanced
skytiger6724skytiger6724
2

test-scenarios

Create test scenarios from user stories with objectives, roles, steps, and outcomes.

Community
Intermediate
tsuji-tomonoritsuji-tomonori

obsidian-doc-check

Validate Obsidian markdown documents against project-specific conventions.

Community
Intermediate
maigenticmaigentic
37

onboarding-flow-optimizer

Define activation events and generate onboarding checklists, tours, and email sequences.

Community
Intermediate