skills.rest
usurobor
usuroborCOMMUNITY
Explore all skills by this author →
GitHub

issue

Create executable issue packs with frontmatter-driven schemas for governance artifacts.

8|Updated Feb 2, 2026
Search Tags:#workflow#documentation#governance#issue#contract#cnos
One-click install
npx skills add https://github.com/usurobor/cnos --skill issue-usurobor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.cdd/skills/cdd/issue
Command: npx skills add https://github.com/usurobor/cnos --skill issue-usurobor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Incoherent or under-specified work requests derail projects. This skill standardizes how issues are written so teams describe the problem, impact, truth, constraints, and acceptance criteria in a single, verifiable artifact.

Core Features & Use Cases

  • Self-contained issue units that encode problem, impact, status truth, source of truth, scope, non-goals, and closure conditions.
  • Frontmatter-driven validation to enforce consistent metadata, traceability, and loader alignment.
  • Embedded guidance for writing contracts, proofs, constraints, and related artifacts, enabling repeatable handoffs and audits.

Quick Start

File a new issue following the contract templates in SKILL.md to demonstrate the end-to-end writing pattern.

Frequently Asked Questions about issue

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

FAQPage Schema
How do I write executable issues that include proof obligations and constraints?▼

Executable issues are written by following a frontmatter-driven schema that encodes contracts, proofs, and constraints directly in the body, ensuring governance artifacts are self-contained, testable, and unambiguous.

What makes a governance issue self-contained and testable?▼

A governance issue becomes self-contained and testable when it standardizes problem descriptions, impact, source of truth, scope, and closure conditions into a single verifiable artifact with required frontmatter validation.

How do I create standardized issue packs for complex workflow changes?▼

Standardized issue packs for complex changes are created by applying frontmatter templates that require fields like name, description, and artifact_class, while embedding implementation guidance and related artifact references.

Does this approach to issue documentation work for both simple and complex changes?▼

Yes, this documentation approach applies to both simple and complex changes by enforcing a consistent schema that names the incoherence, required skills, and implementation guidance for repeatable handoffs and audits.

What is the best way to prevent incoherent or under-specified work requests from derailing projects?▼

The best way to prevent under-specified work requests from derailing projects is standardizing issues to describe the problem, impact, truth, constraints, and acceptance criteria in a single, verifiable artifact.

Related Skills

Explore More Design & Creative Skills→
Davie521Davie521
7

teach-impeccable

Scan a codebase and write design context to .impeccable.md.

Community
Advanced
gonzalezpazmonicagonzalezpazmonica
47

governance-enterprise

Orchestrate enterprise governance workflows for audit trails, compliance, and certifications.

Community
Advanced
shaul1991shaul1991

dashboard

Scan project roots to generate lifecycle status dashboards with ALM governance.

Community
Intermediate
sumik5sumik5
1

capturing-learnings

Automate capture and organization of learnings, errors, and feature requests.

Community
Advanced