osx-concepts

Define OpenSpec-extended concepts, taxonomy, and workflow patterns for AI agents.

6|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/amauryconstant/openspec-extended --skill osx-concepts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: osx-concepts
Source: https://github.com/amauryconstant/openspec-extended/tree/main/resources/claude/skills/osx-concepts
Command: npx skills add https://github.com/amauryconstant/openspec-extended --skill osx-concepts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Foundational knowledge for OpenSpec-extended spec-driven development. It helps teams and AI agents get oriented when starting work, selecting skills, and understanding how extended osx-* concepts augment core skills (osc-*) for cohesive collaboration.

Core Features & Use Cases

  • Skill taxonomy explains the hierarchy between core and extended skills and how they map to real workflows.
  • Artifact concepts defines proposals, specs, design, and tasks, plus delta specs and state flow.
  • Workflow patterns presents common adoption patterns and decision guidance for using OpenSpec in practice.
  • Use Case: when starting a new OpenSpec project, use osx-concepts to ground the approach and align teams.

Quick Start

Read the overview and follow the taxonomy and workflow patterns to orient your OpenSpec work.

Frequently Asked Questions about osx-concepts

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

FAQPage Schema
What are foundational OpenSpec concepts for spec-driven development?

OpenSpec concepts define the taxonomy, artifact concepts, and workflow patterns that align AI agents with spec-driven development paradigms. They cover proposals, specs, design, tasks, and decision frameworks to ground new OpenSpec initiatives.

How do osx-* extensions augment core osc-* skills in OpenSpec?

Extended osx-* skills augment core osc-* skills by providing foundational knowledge and decision frameworks that map hierarchies to real workflows. This ensures cohesive collaboration between teams and AI agents during spec-driven development.

When do I need OpenSpec taxonomy and artifact concepts?

You need OpenSpec taxonomy and artifact concepts when starting a new OpenSpec project to orient your approach. They define proposals, specs, design, tasks, and delta specs to align teams and select appropriate skills.

How do I align AI agents with spec-driven development workflows?

Align AI agents with spec-driven development workflows by applying OpenSpec workflow patterns and decision frameworks. These foundational concepts provide structured guidance and best practices to ensure cohesive collaboration across projects.

Does OpenSpec support delta specs and state flow for project artifacts?

Yes, OpenSpec supports delta specs and state flow as part of its artifact concepts. These define proposals, specs, design, and tasks to manage changes and maintain alignment throughout the spec-driven development lifecycle.

What is the best way to start a new OpenSpec project?

The best way to start a new OpenSpec project is to read the osx-concepts overview and follow the taxonomy and workflow patterns. This grounds your approach, aligns teams, and helps select the right extended skills for cohesive collaboration.