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.
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
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.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.
Utilisation de « spec-driven-implementation ». We need a new workspace invitation flow with several permission states and an uncertain rollout.
RĂ©sultat attendu:
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.
Utilisation de « spec-driven-implementation ». The implementation now supports invitation expiration, but PRODUCT.md does not mention it.
RĂ©sultat attendu:
Utilisation de « spec-driven-implementation ». The feature spans API, persistence, background jobs, and the client.
RĂ©sultat attendu:
TECH.md should document boundaries, data flow, failure handling, dependencies, rollout sequencing, and the test strategy before implementation begins.
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.
Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.
https://skillstore.io/skills/warpdotdev-spec-driven-implementation/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/warpdotdev-spec-driven-implementation?utm_source=security_passport_badge)<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>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@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}
}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"
Turn an ambiguous feature request into a product spec, a technical plan when needed, and clear validation criteria.
Give coding agents stable behavioral and technical context before they implement a cross-cutting change.
Review implementation changes and update the relevant specifications so the repository describes the behavior that actually ships.
Assess this feature request for size, ambiguity, and risk. Recommend whether to write PRODUCT.md, TECH.md, both, or neither. Explain the decision briefly.
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.
Using the approved product behavior and repository context, draft a TECH.md for this feature. Document architecture, interfaces, tradeoffs, risks, dependencies, rollout, and testing.
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.
Auteur
warpdotdevLicence
MIT
RĂ©vision Skillstore
r1
Avis de version
L’auteur n’a déclaré aucune version.
RĂ©f
eb894b254e754cba4a46d73e6e8e54cfe1e3316b
RĂ©cence de maintenance
18/09/2026
Utilisation
0 téléchargements · 0 vues
Structure de fichiers
đź“„ SKILL.md
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 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.
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 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 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.
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.
Planifier des changements de code complexes
par tencentcloudbase
Les changements de code importants échouent souvent lorsque le périmètre, la conception et les critères d’acceptation sont vagues. Cette compétence guide Claude, Codex et Claude Code à travers les exigences, la conception, les tâches et la confirmation par étapes.
Créer des agents Claude Code
par Dami-Randle
Concevoir des agents Claude Code fiables est difficile sans structure. Cette compétence fournit des modèles, des règles de validation et des exemples pour les prompts d’agents, les déclencheurs, les outils et les métadonnées.
Ajouter des outils backend aux agents IA
par AppleLamps
L’ajout d’outils backend peut casser les workflows des agents lorsque les schémas et les gestionnaires ne correspondent pas. Cette skill guide une mise à jour cohérente d’un helper Python, d’un schéma d’outil OpenAI, d’un gestionnaire WebSocket et d’une politique d’accès.
Créer des plans d’implémentation pour les modifications de code
par Cygnusfear
Les modifications de code importantes échouent lorsque les exigences, les fichiers et les étapes de validation ne sont pas clairs. Cette compétence guide Claude, Codex et Claude Code pour produire des plans d’implémentation structurés avant le début du travail.
Tester le code avant la finalisation
par Clouder0
Un travail d’implémentation peut se terminer en laissant passer des échecs. Cette compétence guide Claude, Codex et Claude Code dans l’exécution des tests, du linting et des vérifications de types avant la finalisation.
Planifier les fonctionnalités avant leur implémentation
par DavidOpDeBeeck
Le travail sur les fonctionnalités commence souvent avec un périmètre flou, des risques cachés et des tâches dispersées. Cette compétence crée un plan prêt pour approbation avant le début de l’implémentation.