CommunityProductivité et collaborationgithub.com

warpdotdev/implémentation-pilotée-par-les-spécifications

Adoptez un workflow axé sur les spécifications pour les fonctionnalités importantes : rédigez PRODUCT.md avant l'implémentation, TECH.md si nécessaire, et maintenez les deux à jour au fur et à mesure de l'évolution du développement.

Qu'est-ce que implémentation-pilotée-par-les-spécifications ?

Cette compétence permet d'implémenter un workflow dirigé par les spécifications pour les fonctionnalités de grande envergure. Elle guide l'utilisateur (ou l'agent IA) dans la rédaction préalable d'un document produit (PRODUCT.md) décrivant les objectifs, le contexte et les fonctionnalités attendues, puis d'un document technique (TECH.md) lorsque l'architecture le justifie. Ces spécifications sont versionnées dans le dépôt Git et mises à jour durant le développement, garantissant une traçabilité complète entre la vision produit, les choix techniques et le code final. Idéal pour démarrer une fonctionnalité majeure, planifier du travail en mode agent ou lorsque l'équipe souhaite conserver des spécifications produit et techniques dans le contrôle de source.

Compatible avec~Claude Code~Codex CLI~Cursor

Part ofAgent Workflows

npx skills add https://github.com/warpdotdev/common-skills/tree/main/skills/spec-driven-implementation

Installed? Explore more Productivité et collaboration skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →

Voir l'original→Voir toutes les compétences

Demander à votre IA préférée

Ouvre une nouvelle conversation avec cette compétence d'agent déjà préchargée.

ChatGPT Claude Gemini Grok Perplexity DeepSeek

Documentation

Que fait implémentation-pilotée-par-les-spécifications ?

Adoptez un workflow axé sur les spécifications pour les fonctionnalités importantes en rédigeant PRODUCT.md avant l'implémentation, TECH.md si nécessaire, et en maintenant les deux à jour au fur et à mesure de l'évolution du développement. Utilisez cette approche lorsque vous démarrez une fonctionnalité conséquente, planifiez une implémentation assistée par un agent, ou lorsque l'utilisateur souhaite que les spécifications produit et techniques soient suivies dans le contrôle de source.

Individual skills in this repo

This repo contains 16 individual skills — each has its own dedicated page.

warpdotdev/brandalf

Guides creation, revision, and review of Warp- or Oz-branded assets. Use when working on launch pages, docs, HTML/CSS components, UI mockups, prompts, social assets, copy, presentations, or any other branded deliverable that should look and sound unmistakably Warp or Oz.

warpdotdev/check-impl-against-spec

Compare a pull request's implementation against spec context in spec_context.md and feed any material mismatches into review.json. Use during PR review when approved or repository spec context is available.

warpdotdev/council

Run a model-diverse subagent council to investigate the same problem from multiple perspectives, compare findings, and produce a final recommendation. Use this skill whenever the user asks for a council, second opinions, multiple agents/models to evaluate one question, parallel investigation, red-team/blue-team comparison, or help deciding between competing technical approaches.

warpdotdev/create-pr

Create a pull request in the warp repository for the current branch. Use when the user mentions opening a PR, creating a pull request, submitting changes for review, or preparing code for merge.

warpdotdev/diagnose-ci-failures

Diagnose CI failures for a PR using the GitHub CLI, extract error logs, and generate a plan to fix them. Use when the user asks to check CI status, pull CI issues, triage test failures, or investigate PR build failures.

warpdotdev/fix-errors

Fix compilation errors, linting issues, and test failures in the warp Rust codebase. Covers presubmit checks, WASM-specific errors, and running specific tests. Use when the user hits build errors, clippy or fmt failures, test failures, or needs to run or interpret presubmit before a PR.

warpdotdev/implement-specs

Implement an approved feature from PRODUCT.md and TECH.md, keeping specs and code aligned in the same PR as implementation evolves. Use after the product and tech specs are approved and the next step is building the feature.

warpdotdev/pr-walkthrough

Generate a static interactive D3 walkthrough of a pull request. Use when the user wants a zoomable PR map, graph/canvas PR orientation, or alternate visualization of PR system components, data flow, code dependencies, and user actions.

warpdotdev/reproduce-bug-report

Launch Oz cloud agents with computer use to reproduce UI-focused bug reports, capture visual evidence, and report reproduction findings. Use when investigating a specific interactive or visual bug from an issue, ticket, support report, or prompt.

warpdotdev/resolve-merge-conflicts

Resolve Git merge conflicts by extracting only unresolved paths, conflict hunks, and compact diffs instead of loading whole files into context. Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts, when `git status` shows unmerged paths, or when files contain conflict markers.

warpdotdev/respond-to-pr-comments-in-blocklist

Walk users through PR review comments, fetching and displaying them first when needed, collect per-comment response decisions, apply requested fixes, and preview GitHub replies and resolutions before posting. Use when responding to PR review comments on the current branch.

warpdotdev/review-pr

Review a pull request diff and write structured feedback to review.json for the workflow to publish. Use when reviewing a checked-out PR from local artifacts like pr_diff.txt and pr_description.txt and producing machine-readable review output instead of posting directly to GitHub.

warpdotdev/update-skill

Create or update skills by generating, editing, or refining SKILL.md files in this repository. Use when authoring new skills or revising the structure, frontmatter, or guidance for existing ones.

warpdotdev/validate-changes-match-specs

Validate that a branch or pull request implementation matches introduced product, technical, security, and related specs. Use when reviewing or finishing a spec-driven change and resolving mismatches between checked-in specs and implementation.

warpdotdev/write-product-spec

Write a PRODUCT.md spec for a significant user-facing feature in Warp, focused on detailed behavior and validation. Use when the user asks for a product spec, desired behavior doc, or PRD, wants to define feature behavior before implementation, or when the feature is substantial or behaviorally ambiguous enough that a written spec would improve implementation or review.

warpdotdev/write-tech-spec

Write a TECH.md spec for a significant Warp feature after researching the current codebase and implementation constraints. Use when the user asks for a technical spec, implementation plan, or architecture doc tied to a product spec.

← More Productivité et collaboration skills