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 週前更新