openspec

Enforce a bones-first architectural process for SkullRender projects using OpenSpec.

Updated May 29, 2025
One-click install
npx skills add https://github.com/crozzbite/DnDApp --skill openspec-crozzbite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec
Source: https://github.com/crozzbite/DnDApp/tree/main/.agent/skills/openspec
Command: npx skills add https://github.com/crozzbite/DnDApp --skill openspec-crozzbite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a bones-first architectural process for SkullRender projects by codifying structure and contracts, reducing ambiguity and rework.

Core Features & Use Cases

  • Enforces a bones-first workflow: Proposal, Specs, Design, and Tasks to align teams.
  • Validates artifact contracts using strict schemas and OpenSpec tooling.
  • Enables progress tracking and disciplined handoffs via the OpenSpec CLI.

Quick Start

Initialize a new OpenSpec change by running the openspec CLI to begin the bones-first workflow.

Frequently Asked Questions about openspec

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

FAQPage Schema
What is a bones-first architecture process for software development?

A bones-first architecture process enforces clear structural contracts and schemas across proposal, specs, design, and tasks stages before implementation begins, reducing ambiguity and rework. It codifies artifact structures to align teams early.

How do I enforce strict architectural contracts before implementation?

To enforce strict architectural contracts before implementation, define artifact structures using strict schema definitions for proposals, specs, designs, and tasks. Validating these contracts ensures clear handoffs and reduces ambiguity across the workflow.

How do I start tracking progress for architectural specs using OpenSpec?

Start tracking progress for architectural specs by initializing a new OpenSpec change via the CLI. This begins the bones-first workflow, enabling disciplined handoffs and progress tracking through the proposal, specs, design, and tasks stages.

Does the bones-first workflow require specific artifact schemas for proposals and designs?

Yes, the bones-first workflow requires specific artifact schemas for proposals, specs, designs, and tasks. Strict schema definitions validate the structural contracts to ensure alignment and enable disciplined tracking throughout the project.

When should I use a bones-first design approach instead of direct implementation?

Use a bones-first design approach instead of direct implementation when you need to codify structure and enforce clear contracts upfront to reduce ambiguity. It is essential for aligning teams and validating designs before any code is written.