Openspec Context Loading

forztf/open-skilled-sdd/skills/openspec-context-loading

作者 forztf792f48807c192d740968f56b474e79612c51a98a无许可证10 个星标收录于 2026年10月9日更新于 2026年10月9日仓库10个月前更新

Loads project context, lists existing specs and changes, searches capabilities and requirements. Use when user asks about project state, existing specs, active changes, available capabilities, or needs context discovery. Triggers include "openspec context", "what specs exist", "show changes", "list capabilities", "project context", "find specs", "what's in the spec", "show me specs".

仅含说明Software DevelopmentProductivity & Workflow
AI 生成的概览

通过列出规格、活动变更、需求和能力来加载项目规格上下文。

功能
该技能发现并汇总项目的规格文件、活动与已归档变更、需求及场景。它提供用于列出能力、按关键词搜索以及生成仪表板式概览的 shell 命令模式。输出为结构化摘要和导航提示，而非修改文件。
适用场景
当用户询问存在哪些规格、哪些变更处于活动状态、系统具备哪些能力，或某项功能在何处定义时使用。它适合在着手处理规格或变更之前进行上下文发现。
运行要求
需要项目具备 spec/specs、spec/changes 和 spec/archive 目录结构，以及 find、grep、ls 等 shell 工具，可选 tree 和 bc。该技能不附带脚本，所有命令仅为说明。

Specification Context Loading

Discovers and loads project specifications, active changes, and requirements to provide context.

Quick Start

Context loading helps answer:

  • What specs exist in this project?
  • What changes are currently active?
  • What requirements are defined?
  • What capabilities does the system have?
  • Where is a specific feature specified?

Basic pattern: Search → Read → Summarize

Discovery Commands

List All Specifications

bash
# Find all spec filesfind spec/specs -name "spec.md" -type f
# Find all capability directoriesfind spec/specs -mindepth 1 -maxdepth 1 -type d
# Show spec treetree spec/specs/  # if tree is installed# orls -R spec/specs/

Output format:

spec/specs/├── authentication/│   └── spec.md├── billing/│   └── spec.md└── notifications/    └── spec.md

List Active Changes

bash
# Show all active changesfind spec/changes -maxdepth 1 -type d -not -path "spec/changes" -not -path "*/archive" | sort
# Show with modification datesfind spec/changes -maxdepth 1 -type d -not -path "spec/changes" -not -path "*/archive" -exec ls -ld {} \;
# Count active changesfind spec/changes -maxdepth 1 -type d -not -path "spec/changes" -not -path "*/archive" | wc -l

List Archived Changes

bash
# Show all archived changesls -1 spec/archive/
# Show with datesls -la spec/archive/
# Find recently archived (last 7 days)find spec/archive/ -maxdepth 1 -type d -mtime -7

Search for Requirements

bash
# Find all requirementsgrep -r "### Requirement:" spec/specs/
# Find requirements in specific capabilitygrep "### Requirement:" spec/specs/authentication/spec.md
# List unique requirement namesgrep -h "### Requirement:" spec/specs/**/*.md | sed 's/### Requirement: //' | sort

Search for Scenarios

bash
# Find all scenariosgrep -r "#### Scenario:" spec/specs/
# Count scenarios per specfor spec in spec/specs/**/spec.md; do    count=$(grep -c "#### Scenario:" "$spec")    echo "$spec: $count scenarios"done

Search by Keyword

bash
# Find specs mentioning "authentication"grep -r -i "authentication" spec/specs/
# Find requirements about "password"grep -B 1 -A 5 -i "password" spec/specs/**/*.md | grep -A 5 "### Requirement:"
# Find scenarios about "error"grep -B 1 -A 10 -i "error" spec/specs/**/*.md | grep -A 10 "#### Scenario:"

Common Queries

Query 1: "What specs exist?"

bash
# List all capabilitiesfind spec/specs -mindepth 1 -maxdepth 1 -type d -exec basename {} \;
# Count requirements per capabilityfor cap in spec/specs/*/; do    name=$(basename "$cap")    count=$(grep -c "### Requirement:" "$cap/spec.md" 2>/dev/null || echo "0")    echo "$name: $count requirements"done

Response format:

markdown
## Existing Specifications
The project has specifications for the following capabilities:
- **authentication**: 8 requirements- **billing**: 12 requirements- **notifications**: 5 requirements
Total: 3 capabilities, 25 requirements

Query 2: "What changes are active?"

bash
# List with proposal summariesfor change in spec/changes/*/; do    if [ "$change" != "spec/changes/archive/" ]; then        id=$(basename "$change")        echo "=== $id ==="        head -n 20 "$change/proposal.md" | grep -A 3 "## Why"    fidone

Response format:

markdown
## Active Changes
Currently active changes:
### add-user-auth**Why**: Users need secure authentication...
### update-billing-api**Why**: Payment processing requires v2 API...
Total: 2 active changes

Query 3: "Show me the authentication spec"

bash
# Read full speccat spec/specs/authentication/spec.md
# Or show summaryecho "Requirements:"grep "### Requirement:" spec/specs/authentication/spec.md
echo "\nScenarios:"grep "#### Scenario:" spec/specs/authentication/spec.md

Response format:

markdown
## Authentication Specification
(Include full content of spec.md)
Summary:- 8 requirements- 16 scenarios- Last modified: [date from git log]

Query 4: "Find specs about password"

bash
# Search for keywordgrep -r -i "password" spec/specs/ -A 5
# Show which specs mention itgrep -r -i "password" spec/specs/ -l

Response format:

markdown
## Specs Mentioning "Password"
Found in:- spec/specs/authentication/spec.md (3 requirements)- spec/specs/security/spec.md (1 requirement)
Relevant requirements:### Requirement: Password Validation### Requirement: Password Reset### Requirement: Password Strength

Query 5: "What's in change X?"

bash
# Show full change contextCHANGE_ID="add-user-auth"
echo "=== Proposal ==="cat spec/changes/$CHANGE_ID/proposal.md
echo "\n=== Tasks ==="cat spec/changes/$CHANGE_ID/tasks.md
echo "\n=== Spec Deltas ==="find spec/changes/$CHANGE_ID/specs -name "*.md" -exec echo "File: {}" \; -exec cat {} \;

Dashboard View

Create a comprehensive project overview:

bash
#!/bin/bash# Project specification dashboard
echo "===  Specification Dashboard ==="echo ""
# Capabilitiesecho "## Capabilities"CAPS=$(find spec/specs -mindepth 1 -maxdepth 1 -type d | wc -l)echo "Total capabilities: $CAPS"for cap in spec/specs/*/; do    name=$(basename "$cap")    reqs=$(grep -c "### Requirement:" "$cap/spec.md" 2>/dev/null || echo "0")    echo "  - $name: $reqs requirements"doneecho ""
# Requirementsecho "## Requirements"TOTAL_REQS=$(grep -r "### Requirement:" spec/specs/ | wc -l)TOTAL_SCENARIOS=$(grep -r "#### Scenario:" spec/specs/ | wc -l)echo "Total requirements: $TOTAL_REQS"echo "Total scenarios: $TOTAL_SCENARIOS"echo "Avg scenarios per requirement: $(echo "scale=1; $TOTAL_SCENARIOS/$TOTAL_REQS" | bc)"echo ""
# Changesecho "## Changes"ACTIVE=$(find spec/changes -maxdepth 1 -type d -not -path "spec/changes" -not -path "*/archive" | wc -l)ARCHIVED=$(ls -1 spec/archive/ | wc -l)echo "Active changes: $ACTIVE"echo "Archived changes: $ARCHIVED"echo ""
# Recent activityecho "## Recent Activity"echo "Recently modified specs:"find spec/specs -name "spec.md" -type f -exec ls -lt {} \; | head -5

Response format:

markdown
# Specification Dashboard
## CapabilitiesTotal capabilities: 3  - authentication: 8 requirements  - billing: 12 requirements  - notifications: 5 requirements
## RequirementsTotal requirements: 25Total scenarios: 52Avg scenarios per requirement: 2.1
## ChangesActive changes: 2Archived changes: 15
## Recent ActivityRecently modified specs:- spec/specs/billing/spec.md (2 days ago)- spec/specs/authentication/spec.md (1 week ago)

Advanced Queries

Find Related Requirements

bash
# Find requirements that mention another requirementgrep -r "User Login" spec/specs/ -A 10 | grep "### Requirement:"
# Find cross-referencesgrep -r "See Requirement:" spec/specs/

Analyze Coverage

bash
# Find requirements without scenariosfor spec in spec/specs/**/spec.md; do    awk '/### Requirement:/ {req=$0; getline; if ($0 !~ /#### Scenario:/) print req}' "$spec"done
# Find scenarios without proper Given/When/Thengrep -A 5 "#### Scenario:" spec/specs/**/*.md | grep -v "GIVEN\|WHEN\|THEN"

Compare Active vs Archive

bash
# Show evolution over timeecho "Archive history:"ls -1 spec/archive/ | head -10
echo "Recent archives (last 30 days):"find spec/archive/ -maxdepth 1 -type d -mtime -30 -exec basename {} \;

Search Patterns

Pattern 1: Capability Discovery

User asks: "What can the system do?"

bash
# List capabilitiesfind spec/specs -mindepth 1 -maxdepth 1 -type d -exec basename {} \;
# Show high-level requirementsfor cap in spec/specs/*/; do    echo "=== $(basename $cap) ==="    grep "### Requirement:" "$cap/spec.md" | head -3done

Pattern 2: Feature Search

User asks: "Is there a spec for password reset?"

bash
# Search for keywordgrep -r -i "password reset" spec/specs/ -B 1 -A 10
# If found, show full requirementgrep -B 1 -A 20 "Requirement:.*Password Reset" spec/specs/**/*.md

Pattern 3: Change Tracking

User asks: "What's being worked on?"

bash
# Show active changes with statusfor change in spec/changes/*/; do    if [ "$change" != "spec/changes/archive/" ]; then        id=$(basename "$change")        echo "$id:"        test -f "$change/IMPLEMENTED" && echo "  Status: Implemented" || echo "  Status: In Progress"        echo "  Tasks: $(grep -c "^[0-9]\+\." "$change/tasks.md")"    fidone

Best Practices

Pattern 1: Provide Context Before Details

Good flow:

markdown
1. Show dashboard (high-level overview)2. User asks about specific capability3. Show that capability's requirements4. User asks about specific requirement5. Show full requirement with scenarios

Pattern 2: Use Grep Efficiently

bash
# Combine filters for precisiongrep -r "### Requirement:" spec/specs/ | grep -i "auth"
# Use context flags for readabilitygrep -B 2 -A 10 "#### Scenario:" spec/specs/authentication/spec.md

Pattern 3: Aggregate Information

Don't just dump file contents. Summarize:

markdown
**Bad**: (dump entire spec file)
**Good**:"The authentication spec has 8 requirements covering:- User login- Password management- Session handling- Multi-factor authentication
Would you like details on any specific requirement?"

Anti-Patterns to Avoid

Don't:

  • Read entire spec files without user request
  • List every single requirement by default
  • Show raw grep output without formatting
  • Assume user knows capability names

Do:

  • Start with high-level overview
  • Ask which area user wants to explore
  • Format output clearly
  • Provide navigation hints

Reference Materials

  • SEARCH_PATTERNS.md [blocked] - Advanced grep/find patterns

Token budget: This SKILL.md is approximately 460 lines, under the 500-line recommended limit.

来源与署名

来源：forztf/open-skilled-sdd位于skills/openspec-context-loading提交792f488

许可证： 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架

更多来自 forztf/open-skilled-sdd 的技能

Openspec Proposal Creation

forztf

创建规范驱动的变更提案，包含提案文档、任务清单和 EARS 格式的规范增量。

Software Development1010个月前更新

Openspec Archiving

forztf

归档已完成的 OpenSpec 变更提案，并将其规格增量合并到现行规格文档中。

AI & Agents1010个月前更新

更多Software Development技能

Playground

anthropics

精选

构建自包含的交互式 HTML 演练场，包含控件、实时预览和可复制的提示词输出。

Software Development37K今天更新

M5 Onboard

anthropics

精选

通过 USB 检测 M5Stack ESP32 开发板，刷写 UIFlow 2.0 固件并安装 MicroPython 应用包。

Software Development37K今天更新

Cardputer Buddy

anthropics

精选

指导迭代 Cardputer-Adv 的 MicroPython 应用包：添加应用、通过 USB 串口推送文件、查看日志并运行 REPL 命令。

Software Development37K今天更新

Web Design Guidelines

vercel-labs

精选

依据从远程来源获取的 Web Interface Guidelines 审查 UI 代码，并以 file:line 形式报告问题。

Software Development32K5周前更新

Vercel React Native Skills

vercel-labs

精选

React Native 与 Expo 最佳实践规则，涵盖列表性能、动画、导航、UI 模式、状态与 monorepo 配置。

Software Development32K5周前更新

Vercel React Best Practices

vercel-labs

精选

Vercel 的 React 与 Next.js 性能指南，以 70 条规则的形式用于编写、审查和重构代码。

Software Development32K5周前更新