spec-reference

Retrieve and organize SaaS platform specifications, requirements, APIs, and test definitions.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/Takas0522/ai-sldc-demo-takas-2603 --skill spec-reference-takas0522
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-reference
Source: https://github.com/Takas0522/ai-sldc-demo-takas-2603/tree/main/.github/skills/spec-reference
Command: npx skills add https://github.com/Takas0522/ai-sldc-demo-takas-2603 --skill spec-reference-takas0522

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

このスキルは、SaaS管理プラットフォームの仕様書やテスト資料を探し回る手間を減らし、必要な要件・ルール・API・データモデルを素早く参照できるようにします。

Core Features & Use Cases

  • 仕様の横断参照: 機能要件、ビジネスルール、API仕様、データモデル、セキュリティ要件を一つの起点から確認できます。
  • トレーサビリティ確認: BR、FR、API、テストIDの対応関係を追跡し、影響範囲の把握やレビューを支援します。
  • テスト・実装判断の補助: ユニットテストやE2Eテストの確認、正本仕様と補助資料の差分把握に役立ちます。
  • Use Case: ある機能の仕様確認時に、関連する要件、API、セキュリティ、テスト仕様をまとめて洗い出したい場面で使います。

Quick Start

仕様書リファレンススキルを使って、対象機能の要件IDと関連API、テスト仕様をまとめて確認してください。

Frequently Asked Questions about spec-reference

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

FAQPage Schema
How do I trace SaaS requirements from business rules to API and test definitions?

Trace SaaS requirements by retrieving business rules, functional requirements, API specifications, and test definitions from canonical documentation to verify BR to FR to API to test traceability for impact analysis.

What is the best way to find SaaS API specifications and data models for feature verification?

Finding SaaS API specifications and data models involves organizing platform requirements, rules, and interfaces from a canonical documentation set to support feature verification and architecture reference.

Can I retrieve role-based security requirements and unit test definitions for a specific SaaS feature?

Retrieve role-based security requirements and unit test definitions by looking up feature specifications, security rules, and E2E test definitions from the canonical SaaS documentation set.

How do I compare current SaaS specifications against legacy source documents?

Compare current SaaS specifications against legacy source documents by retrieving organized platform requirements and interfaces to identify differences between canonical specs and supplementary materials.

Does this specification retrieval approach work for E2E test planning and security review?

Specification retrieval supports E2E test planning and security review by extracting test definitions, role-based security lookups, and interface references from the canonical SaaS documentation set.

When do I need cross-referencing for SaaS platform specifications and architecture interfaces?

Cross-referencing SaaS platform specifications is needed when verifying feature requirements, confirming architecture interfaces, or planning tests to consolidate scattered rules, APIs, and data models into a single reference point.