スキル spec-driven-development

📦

spec-driven-development

Name: spec-driven-development
Author: addyosmani

コンテンツリビジョン r2 安全 ⚙️ 外部コマンド

Plan Software Work With Clear Specifications

Unclear requirements cause rework, missed assumptions, and poorly ordered implementation tasks. This skill guides teams through reviewed specifications, dependency-aware plans, and verifiable tasks before coding.

対応: Claude Codex Code(CC)

🥉 78 ブロンズ

自分のエージェントでインストール

このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。

エージェントリクエスト

Review the Skillstore skill "spec-driven-development" from https://skillstore.io/skills/addyosmani-spec-driven-development.md and its manifest at https://skillstore.io/api/skills/addyosmani-spec-driven-development/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。

エージェントが読めるリソース

AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。

Markdown詳細 GET /skills/addyosmani-spec-driven-development.md 署名済み manifest GET /api/skills/addyosmani-spec-driven-development/manifest 署名済み lockfile GET /api/skills/addyosmani-spec-driven-development/lockfile

テストする

「spec-driven-development」を使用しています。 Make the dashboard faster.

期待される結果:

Success criteria: largest contentful paint under 2.5 seconds on a 4G connection; initial data load under 500 milliseconds; cumulative layout shift under 0.1.

「spec-driven-development」を使用しています。 Build account, billing, notifications, and reporting capabilities.

期待される結果:

Capability map: identity owns accounts and sessions; billing depends on identity; notifications depends on identity; reporting depends on billing and notifications.
Build order: identity, then billing and notifications, then reporting.

セキュリティ監査

安全

v2 • 2026/9/19 バージョン別レポートを開く

All 26 static findings are false positives. The flagged backticks are Markdown code formatting and inline references in a documentation workflow, not shell execution or system reconnaissance.

スキャンされたファイル

252

解析済み行数

レビュー項目

誤検知を無視

最新の完了済み静的・セマンティック監査では、確認済みのセキュリティ検出事項は見つかりませんでした。これは、スキルに副作用がないことを証明するものではありません。

監査者: codex 監査履歴を表示 →

このレポートを共有・引用

バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。

バージョン別レポートを開く

レポートリンクをコピー

https://skillstore.io/skills/addyosmani-spec-driven-development/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdownバッジ

[![Skillstore security assessment](https://skillstore.io/badges/skills/addyosmani-spec-driven-development/security.svg)](https://skillstore.io/skills/addyosmani-spec-driven-development?utm_source=security_passport_badge)

HTMLバッジ

<a href="https://skillstore.io/skills/addyosmani-spec-driven-development?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-spec-driven-development/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

埋め込みカード

<iframe src="https://skillstore.io/embed/skills/addyosmani-spec-driven-development.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

学術引用 (APA · BibTeX · CFF)

APA形式の引用

addyosmani. (2026). spec-driven-development security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-spec-driven-development/audits/2

BibTeX形式の引用

@techreport{addyosmani-addyosmani-spec-driven-development-2026,
  author = {addyosmani},
  title = {spec-driven-development security audit report (audit version 2)},
  institution = {Skillstore},
  year = {2026},
  number = {2},
  url = {https://skillstore.io/skills/addyosmani-spec-driven-development/audits/2},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "spec-driven-development security audit report (audit version 2)"
version: "unspecified"
type: report
authors:
  - name: "addyosmani"
date-released: "2026-09-19"
url: "https://skillstore.io/skills/addyosmani-spec-driven-development/audits/2"
identifiers:
  - type: other
    value: "skillstore:addyosmani-spec-driven-development:audit:2"
    description: "Skillstore immutable audit report identifier"

バリアントを比較

インストール可能なバリアント 2 件

各作者のスキルは個別のインストール項目として維持されます。推奨バリアントは Skillstore の証拠で順位付けされます。

このバリアントが首位の理由

Skillstore スコアが最高

作者 / ソース Skillstore スコア証拠の信頼度 Skillstore 利用状況更新済み

Joseph OBrien 推奨

89jobrien-spec-driven-development

Skillstore スコア 81

証拠の信頼度高

Skillstore 利用状況 20

更新済み

2026-09-09

addyosmani 現在

addyosmani-spec-driven-development

Skillstore スコア 78

証拠の信頼度中

Skillstore 利用状況 0

更新済み

2026-09-22

Skillstore スコア

このスコアの理由証拠の信頼度: 中

アーキテクチャ

保守性

コンテンツ

コミュニティ

仕様準拠

作成できるもの

Shape a New Product Feature

Turn an initial feature idea into an approved specification with user goals, boundaries, success criteria, and an implementation plan.

Decompose a Multi-Module Initiative

Map independently testable capabilities, record dependency direction, and create module-specific specifications in build order.

Make Requirements Testable

Convert vague outcomes into measurable acceptance criteria, verification steps, and focused implementation tasks.

これらのプロンプトを試す

Draft a Basic Specification

Create a concise specification for this feature: [feature]. Ask clarifying questions first, then define the objective, users, scope, success criteria, and open questions.

Clarify an Ambiguous Request

Review this request: [request]. List the assumptions you would need to confirm, ask focused questions, and reframe the final requirements as testable success criteria.

Plan a Multi-Module Change

Decompose this initiative into independently testable modules: [initiative]. Create a capability map with stable identifiers, dependencies, build order, and a specification outline for each module.

Prepare Implementation Tasks

Using this approved specification and plan: [documents], create dependency-ordered tasks. Give each task acceptance criteria, a verification step, and the files or areas likely to change.

ベストプラクティス

Confirm assumptions before drafting specification content.
Use stable module identifiers and explicit dependency direction.
Require human approval at each phase before advancing.

回避

Starting implementation before requirements and success criteria are approved.
Hiding ambiguous decisions inside a specification without asking.
Creating tasks without acceptance criteria or a verification step.

よくある質問

When should I use this skill?

Use it for new projects, significant features, ambiguous requirements, or changes that span multiple modules.

When should I skip it?

Skip it for single-line fixes, typo corrections, and small changes with clear requirements.

Does it write production code?

No. It prepares specifications, plans, tasks, and review gates before implementation.

What does the specification include?

It covers the objective, commands, project structure, code style, testing strategy, boundaries, success criteria, and open questions.

How does it handle large initiatives?

It creates a capability map, records dependencies, sets a build order, and creates a specification for each module.

Does it replace technical review?

No. Human reviewers still approve assumptions, scope, architecture, security concerns, and readiness for implementation.

開発者情報

作成者

addyosmani

ライセンス

MIT

Skillstore リビジョン

バージョンに関する注意

作者はバージョンを宣言していません。

リポジトリ

https://github.com/addyosmani/agent-skills/tree/c004a74784a08295d52749b04cda634125b9a581/skills/spec-driven-development

参照

5d5054f8a23586f9b500fece1cb613a9dffc787b

メンテナンスの新しさ

2026/9/19

利用状況

0 ダウンロード · 0 閲覧

ファイル構成

📄 SKILL.md

addyosmani のその他のスキル

すべて表示

📦

code-review-and-quality

5つの品質軸でコードをレビュー

コード変更には、正確性、セキュリティ、アーキテクチャ、可読性、パフォーマンスに関する問題が潜んでいる可能性があります。このスキルは、体系的なレビュープロセスを適用し、優先順位が明確で実行可能なフィードバックを提供します。

コーディング＆開発表示

📦

interview-me

Clarify User Intent Before You Build

Underspecified requests cause teams to build the wrong outcome and discover misalignment late. This skill runs a focused, one-question interview that turns ambiguity into confirmed intent.

コミュニケーション表示

📦

planning-and-task-breakdown

Plan Work Into Verifiable Tasks

Large or vague software work can hide dependencies, missing acceptance criteria, and verification gaps. This skill converts a specification into ordered task slices with checkpoints, scope guidance, and clear completion conditions.

生産性表示

📦

documentation-and-adrs

Document Decisions and Architecture Clearly

Teams lose context when important technical decisions remain in chat, code comments, or individual memory. This skill turns architectural reasoning, API guidance, project instructions, and release changes into structured documentation.

ドキュメント表示

📦

frontend-ui-engineering

Build Accessible, Production-Ready Frontends

Frontend work can become inconsistent, inaccessible, or difficult to maintain. This skill guides component architecture, responsive layouts, state handling, and polished user experiences.

デザイン＆クリエイティブ表示

📦

debugging-and-error-recovery

Debug Errors with a Root-Cause Workflow

Debugging failures by guesswork wastes time and can hide the real cause. This skill provides a repeatable process for reproducing, isolating, fixing, and verifying problems.

コーディング＆開発表示

すべて表示

📦