Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

vcsdd-spec-crystallization

Estrellas27

Forks4

Actualizado1 de abril de 2026 a las 08:58

Use this skill when writing Phase 1a behavioral specifications in VCSDD. Provides EARS format requirements writing, purity boundary analysis, edge case enumeration, and spec quality validation patterns.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

sc30gsw

sc30gsw/vcsdd-claude-code

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Especialistas en gestión de proyectosOperaciones empresariales y financieras·SOC 13-1082

SKILL.md

readonly

name	vcsdd-spec-crystallization
description	Use this skill when writing Phase 1a behavioral specifications in VCSDD. Provides EARS format requirements writing, purity boundary analysis, edge case enumeration, and spec quality validation patterns.
origin	VCSDD

VCSDD Spec Crystallization

When to Activate

Phase 1a of VCSDD pipeline (behavioral specification)
Writing EARS-format requirements
Identifying edge cases for a feature
Reviewing a behavioral spec for completeness

EARS Requirement Format

Every requirement MUST use EARS (Easy Approach to Requirements Syntax):

Pattern	Syntax	Example
Ubiquitous	THE SYSTEM SHALL [action]	THE SYSTEM SHALL log all authentication attempts
Event-driven	WHEN [trigger] THE SYSTEM SHALL [action]	WHEN user submits empty form THE SYSTEM SHALL return ErrorCode.EMPTY
State-driven	WHILE [state] THE SYSTEM SHALL [action]	WHILE user is authenticated THE SYSTEM SHALL display dashboard
Conditional	IF [condition] THEN THE SYSTEM SHALL [action]	IF retry count exceeds 3 THEN THE SYSTEM SHALL lock account
Optional	WHERE [feature] THE SYSTEM SHALL [action]	WHERE audit mode enabled THE SYSTEM SHALL record all reads

Spec Completeness Checklist

Every requirement has a unique ID (REQ-001, REQ-002, ...)
Every requirement uses EARS syntax
Every requirement is testable (can be pass/fail verified)
Edge case catalog includes: empty inputs, boundary values, concurrent access, error conditions
Non-functional requirements specified (performance bounds, security constraints)
Purity boundary identified: pure core vs effectful shell

Purity Boundary Analysis

Separate code into:

Pure Core: deterministic functions, no side effects, same input → same output always
- Example: parsing logic, business rules, validation, calculations
- Formally verifiable with Kani/hypothesis/fast-check
Effectful Shell: I/O, database, network, time, randomness
- Example: file readers, HTTP clients, database queries
- Tested with integration tests and mocks at the boundary

Edge Case Catalog Template

## Edge Cases

### Input Edge Cases
- Empty input: [expected behavior]
- Maximum length input: [expected behavior]
- Special characters / unicode: [expected behavior]
- Null / undefined: [expected behavior]

### State Edge Cases
- First-time run (no state): [expected behavior]
- Concurrent modification: [expected behavior]
- Interrupted operation: [expected behavior]

### Error Edge Cases
- External dependency unavailable: [expected behavior]
- Partial failure: [expected behavior]
- Timeout: [expected behavior]

Más de este repositorio

mismo repositorio

vcsdd-adversarial-refinement

sc30gsw/vcsdd-claude-code

Use this skill when running or interpreting VCSDD adversarial reviews. Provides calibration guidance for the Adversary agent, finding severity classification, and anti-leniency enforcement patterns.

2026-04-0127

vcsdd-adversary

sc30gsw/vcsdd-claude-code

Run Phase 3 (adversarial review) for the active VCSDD feature. Spawns a fresh vcsdd-adversary agent with zero Builder context to review implementation against spec. Produces binary PASS/FAIL verdict per dimension.

2026-04-0127

vcsdd-commit

sc30gsw/vcsdd-claude-code

Create a git commit for the current VCSDD phase. Auto-generates a conventional commit message from state.json including phase, sprint, gate verdict, and affected bead IDs. Tags with vcsdd/<feature>/phase-<id>.

2026-04-0127

vcsdd-contract-review

sc30gsw/vcsdd-claude-code

Run the strict-mode sprint contract review after Phase 2c. Spawns a fresh vcsdd-adversary instance to review `contracts/sprint-N.md` and writes a PASS/FAIL verdict under `reviews/contracts/sprint-N/output/`.

2026-04-0127

vcsdd-converge

sc30gsw/vcsdd-claude-code

Run Phase 6 (convergence check) for the active VCSDD feature. Validates four-dimensional convergence: finding diminishment, finding specificity, criteria coverage, and duplicate detection.

2026-04-0127

vcsdd-convergence-detection

sc30gsw/vcsdd-claude-code

Use this skill during Phase 6 convergence checks. Provides four-dimensional convergence analysis, hallucination detection, and duplicate finding identification.

2026-04-0127

VCSDD Spec Crystallization

When to Activate

Phase 1a of VCSDD pipeline (behavioral specification)

Writing EARS-format requirements

Identifying edge cases for a feature

Reviewing a behavioral spec for completeness

EARS Requirement Format

Every requirement MUST use EARS (Easy Approach to Requirements Syntax):

Pattern

Syntax

Example

Ubiquitous

THE SYSTEM SHALL [action]

THE SYSTEM SHALL log all authentication attempts

Event-driven

WHEN [trigger] THE SYSTEM SHALL [action]

WHEN user submits empty form THE SYSTEM SHALL return ErrorCode.EMPTY

State-driven

WHILE [state] THE SYSTEM SHALL [action]

WHILE user is authenticated THE SYSTEM SHALL display dashboard

Conditional

IF [condition] THEN THE SYSTEM SHALL [action]

IF retry count exceeds 3 THEN THE SYSTEM SHALL lock account

Optional

WHERE [feature] THE SYSTEM SHALL [action]

WHERE audit mode enabled THE SYSTEM SHALL record all reads

Spec Completeness Checklist

Every requirement has a unique ID (REQ-001, REQ-002, ...)

Every requirement uses EARS syntax

Every requirement is testable (can be pass/fail verified)

Edge case catalog includes: empty inputs, boundary values, concurrent access, error conditions

Non-functional requirements specified (performance bounds, security constraints)

Purity boundary identified: pure core vs effectful shell

Purity Boundary Analysis

Separate code into:

Pure Core: deterministic functions, no side effects, same input → same output always

Example: parsing logic, business rules, validation, calculations
Formally verifiable with Kani/hypothesis/fast-check

Effectful Shell: I/O, database, network, time, randomness

Example: file readers, HTTP clients, database queries
Tested with integration tests and mocks at the boundary

Edge Case Catalog Template

## Edge Cases ### Input Edge Cases - Empty input: [expected behavior] - Maximum length input: [expected behavior] - Special characters / unicode: [expected behavior] - Null / undefined: [expected behavior] ### State Edge Cases - First-time run (no state): [expected behavior] - Concurrent modification: [expected behavior] - Interrupted operation: [expected behavior] ### Error Edge Cases - External dependency unavailable: [expected behavior] - Partial failure: [expected behavior] - Timeout: [expected behavior]