skills.rest
Michael0520
Michael0520COMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-context-loading

Load and aggregate specifications, changes, capabilities, and requirements from a repository.

Updated Mar 31, 2026
Search Tags:#requirements#specifications#search#discovery#capabilities#changes#context-loading
One-click install
npx skills add https://github.com/Michael0520/milo.me --skill openspec-context-loading
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-context-loading
Source: https://github.com/Michael0520/milo.me/tree/main/.claude/skills/openspec-context-loading
Command: npx skills add https://github.com/Michael0520/milo.me --skill openspec-context-loading

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams quickly understand a project's state by loading and presenting specifications, changes, capabilities, and requirements, reducing time spent on manual state gathering.

Core Features & Use Cases

  • Load and expose the list of existing specs and active changes to stakeholders.
  • Show available capabilities and requirements to answer "what exists" and "what's changing" across the project.
  • Support context-driven conversations by providing structured summaries that guide decision-making.

Quick Start

  • Run discovery commands to inspect specs: find spec/specs -name "spec.md" -type f
  • List active changes: find spec/changes -maxdepth 1 -type d -not -path "spec/changes/archive" | sort
  • List archived changes: ls -1 spec/archive/
  • Inspect requirements and scenarios: grep -r "### Requirement:" spec/specs/
  • Explore capabilities: grep -h "#### Scenario:" spec/specs/**/*.md | sed 's/#### Scenario: //'

Frequently Asked Questions about openspec-context-loading

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

FAQPage Schema
How do I discover existing project specifications and active changes in a repository?▼

You can discover project specifications and active changes by running file discovery commands to locate spec.md files and enumerate change directories, providing a structured summary of the repository's current state.

What is the best way to find archived changes and available capabilities in a project?▼

The best way to find archived changes and available capabilities is to list archived directories and grep for scenario headers within specification files, surfacing the project's capability tree and historical modifications.

How do I extract and list all requirements and scenarios from project specification files?▼

You can extract and list requirements and scenarios from project specification files by using grep to recursively search for '### Requirement:' and '#### Scenario:' headers, surfacing structured context for decision-making.

Can I use this context loading approach to support stakeholders asking what is changing across the project?▼

Yes, you can use this context loading approach to support stakeholders by exposing the list of existing specs, active changes, and available capabilities, reducing time spent on manual state gathering.

Do I need a specific directory structure to load project specs and enumerate changes?▼

You need a specific directory structure to load project specs and enumerate changes, specifically expecting directories like spec/specs for specification files and spec/changes for active and archived change records.

Related Skills

Explore More Software Engineering Skills→
pradeepmoulipradeepmouli
2

speckit-baseline

Generate baseline-spec.md and current-state.md from repository analysis.

Community
Advanced
bug-opsbug-ops
11

sdd

Guide users through Spec-Driven Development phases from specification to review.

Community
Advanced
patmaddoxpatmaddox

gap-analysis

Compare commit message intent against codebase state to identify functional gaps.

Community
Intermediate
harleypigharleypig
3

write-documentation

Generate README, API references, and changelogs from source code.

Community
Advanced