스킬 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 브론즈

Maintain this Skill? Claim it 🥉 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 근거로 순위가 정해집니다.

이 변형이 1위인 이유

Skillstore 점수가 가장 높음

작성자 / 소스 Skillstore 점수 증거 신뢰도 Skillstore 사용량 업데이트됨

Joseph OBrien 권장

89jobrien-spec-driven-development

Skillstore 점수 81

증거 신뢰도 높음

Skillstore 사용량 30

업데이트됨

2026-10-19

addyosmani 현재

addyosmani-spec-driven-development

Skillstore 점수 78

증거 신뢰도 중간

Skillstore 사용량 6

업데이트됨

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의 다른 스킬

전체 보기

📦

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.

커뮤니케이션 보기

📦

code-review-and-quality

다섯 가지 품질 기준으로 코드 검토

코드 변경에는 정확성, 보안, 아키텍처, 가독성 및 성능 문제가 숨어 있을 수 있습니다. 이 스킬은 체계적인 검토 프로세스를 적용하여 우선순위가 명확하고 실행 가능한 피드백을 제공합니다.

코딩 및 개발 보기

📦

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.

디자인 및 크리에이티브 보기

📦

security-and-hardening

Harden Applications Against Security Risks

Security reviews can miss trust boundaries and unsafe data flows. This skill supplies threat-modeling prompts, OWASP patterns, and practical review checklists.

보안 및 컴플라이언스 보기

전체 보기

📦