스킬 spec-driven-implementation

📦

spec-driven-implementation

Name: spec-driven-implementation
Author: warpdotdev

콘텐츠 리비전 r1 안전 ⚙️ 외부 명령어

Plan Features With Living Specs

Substantial feature work can become ambiguous when product intent, technical decisions, and implementation drift apart. This skill guides agents through practical product and technical specifications that stay aligned with shipped work.

지원: Claude Codex Code(CC)

🥉 78 브론즈

Maintain this Skill? Claim it 🥉 78 브론즈

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청

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

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/warpdotdev-spec-driven-implementation.md 서명된 manifest GET /api/skills/warpdotdev-spec-driven-implementation/manifest 서명된 lockfile GET /api/skills/warpdotdev-spec-driven-implementation/lockfile

테스트해 보기

"spec-driven-implementation" 사용 중입니다. We need a new workspace invitation flow with several permission states and an uncertain rollout.

예상 결과:

Recommendation: write PRODUCT.md first and TECH.md after the permission model is settled. The request has user-facing edge cases, cross-cutting behavior, and rollout risk.

"spec-driven-implementation" 사용 중입니다. The implementation now supports invitation expiration, but PRODUCT.md does not mention it.

예상 결과:

Update PRODUCT.md with expiration behavior and recovery rules.
Add success criteria for expired invitations.
Add tests that cover expiration and re-invitation.

"spec-driven-implementation" 사용 중입니다. The feature spans API, persistence, background jobs, and the client.

예상 결과:

TECH.md should document boundaries, data flow, failure handling, dependencies, rollout sequencing, and the test strategy before implementation begins.

보안 감사

안전

v1 • 2026. 9. 18. 버전별 보고서 열기

All 23 static findings are false positives: the detector matched Markdown inline-code spans in SKILL.md, not executable Ruby or shell commands. The reviewed skill describes a specification workflow and contains no evidence of prompt injection, network activity, credential access, or data exfiltration.

스캔된 파일

144

분석된 줄 수

검토 항목

오탐 무시됨

위험 요인

가장 최근에 완료된 정적·의미론적 감사에서 확인된 보안 발견 사항이 감지되지 않았습니다. 이는 스킬에 부작용이 없음을 증명하지 않습니다.

감사자: codex

이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기

보고서 링크 복사

https://skillstore.io/skills/warpdotdev-spec-driven-implementation/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 배지

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

HTML 배지

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

임베드 카드

<iframe src="https://skillstore.io/embed/skills/warpdotdev-spec-driven-implementation.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 인용

warpdotdev. (2026). spec-driven-implementation security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/warpdotdev-spec-driven-implementation/audits/1

BibTeX 인용

@techreport{warpdotdev-warpdotdev-spec-driven-implementation-2026,
  author = {warpdotdev},
  title = {spec-driven-implementation security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/warpdotdev-spec-driven-implementation/audits/1},
  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-implementation security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "warpdotdev"
date-released: "2026-09-18"
url: "https://skillstore.io/skills/warpdotdev-spec-driven-implementation/audits/1"
identifiers:
  - type: other
    value: "skillstore:warpdotdev-spec-driven-implementation:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간

아키텍처

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

Plan a Large Feature

Turn an ambiguous feature request into a product spec, a technical plan when needed, and clear validation criteria.

Coordinate Agent Implementation

Give coding agents stable behavioral and technical context before they implement a cross-cutting change.

Keep Documentation Current

Review implementation changes and update the relevant specifications so the repository describes the behavior that actually ships.

이 프롬프트를 사용해 보세요

Decide If Specs Are Needed

Assess this feature request for size, ambiguity, and risk. Recommend whether to write PRODUCT.md, TECH.md, both, or neither. Explain the decision briefly.

Draft a Product Spec

Write a PRODUCT.md for this feature. Cover the user problem, intended behavior, invariants, edge cases, success criteria, and validation approach. Keep implementation details separate.

Create a Technical Spec

Using the approved product behavior and repository context, draft a TECH.md for this feature. Document architecture, interfaces, tradeoffs, risks, dependencies, rollout, and testing.

Audit Specs Against Implementation

Compare PRODUCT.md and TECH.md with the current implementation and tests. List behavior or architecture drift, then propose precise spec updates and missing verification.

모범 사례

Write product behavior before choosing implementation details.
Use a technical specification when boundaries, tradeoffs, or risks are meaningful.
Update specifications whenever shipped behavior or architecture changes.

피하기

Do not write specifications for routine changes that gain no clarity from them.
Do not let technical details replace user-facing behavior and success criteria.
Do not leave specifications unchanged after implementation diverges from the plan.

자주 묻는 질문

When should I use this skill?

Use it for substantial, ambiguous, cross-cutting, or risky feature work where shared written context improves implementation and review.

Is a technical specification always required?

No. Use TECH.md when architecture, tradeoffs, dependencies, or testing decisions need explicit documentation.

What belongs in PRODUCT.md?

Describe the user problem, desired behavior, invariants, edge cases, success criteria, and how the result will be validated.

What belongs in TECH.md?

Describe implementation boundaries, interfaces, architecture, tradeoffs, risks, dependencies, rollout, and testing.

Can this skill implement the feature?

It guides implementation from approved specifications, but the implementation requires a coding agent and the target repository.

How do I keep specifications accurate?

Compare them with code and tests during implementation, then update them whenever behavior, architecture, risks, or validation changes.

개발자 세부 정보

작성자

warpdotdev

라이선스

MIT

Skillstore 리비전

버전 안내

작성자가 버전을 선언하지 않았습니다.

리포지토리

https://github.com/warpdotdev/common-skills/tree/69b4753651ab7fab518c82be087b9f1d5b966631/.agents/skills/spec-driven-implementation

참조

eb894b254e754cba4a46d73e6e8e54cfe1e3316b

유지보수 최신성

2026. 9. 18.

사용량

0 다운로드 · 0 조회

파일 구조

📄 SKILL.md

warpdotdev의 다른 스킬

전체 보기

📦

council

Compare Decisions with an AI Council

Complex decisions can suffer from narrow analysis and hidden assumptions. This skill coordinates diverse agents, compares their evidence, and produces one actionable recommendation.

생산성 보기

📦

migrate-to-factory

Migrate Workflows to Factory

Moving an existing agent workflow into Factory can create duplicate roles, broken paths, or conflicting handoffs. This skill guides a focused migration into an existing Factory repository and validates the resulting configuration.

DevOps 및 인프라 보기

📦

respond-to-pr-comments-in-blocklist

Resolve Pull Request Feedback Safely

Pull request feedback can be difficult to track, implement, and answer consistently. This skill guides each decision, validates accepted changes, and previews GitHub responses before posting.

코딩 및 개발 보기

📦

write-product-spec

Write Clear Product Specifications

Turn ambiguous feature requests into structured product specifications that align design, engineering, and review. This skill defines user-visible behavior, scope, references, open questions, and handoff details in a consistent PRODUCT.md format.

생산성 보기

📦

diagnose-ci-failures

Diagnose CI Failures Faster

CI failures can hide the first useful error among checks, logs, and repeated noise. This skill gathers relevant GitHub evidence and produces a prioritized plan for repair.

DevOps 및 인프라 보기

📦

research

Delegate Broad Codebase Research

Large investigations can flood the primary agent context with irrelevant files and logs. This skill delegates read-only research and returns concise conclusions with cited evidence.

연구 및 학습 보기

전체 보기

📦