Draft Warp Feature Documentation
Feature specifications do not automatically become accurate, publishable documentation. This skill verifies implementation details, confirms audience and structure, drafts MDX, and prepares a reviewable pull request.
ArrĂȘtez-vous et demandez confirmation avant lâinstallation.
Examinez le plan et obtenez le consentement explicite de lâutilisateur avant de modifier des fichiers.
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
Review the Skillstore skill "write-feature-docs" from https://skillstore.io/skills/warpdotdev-write-feature-docs.md and its manifest at https://skillstore.io/api/skills/warpdotdev-write-feature-docs/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.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 « write-feature-docs ». Document APP-1234 from its product and technical specifications.
RĂ©sultat attendu:
A confirmed content design plan, a concise outline with verification labels, and a complete MDX feature page ready for review.
Utilisation de « write-feature-docs ». Create documentation for a shipped feature that has no specification.
RĂ©sultat attendu:
A research summary, targeted questions for unresolved behavior, and a documentation draft based on confirmed repository evidence.
Utilisation de « write-feature-docs ». Update the existing Agent Mode page and prepare a draft pull request.
RĂ©sultat attendu:
Most detections are Markdown backticks, code fences, relative links, or benign GitHub examples and are false positives. The fixed pull request body path creates a local tampering risk, and optional UI capture can expose sensitive data when images enter a public documentation change. No prompt injection or malicious intent was found.
Il sâagit de capacitĂ©s locales rĂ©elles qui peuvent ĂȘtre attendues pour cette compĂ©tence ; elles nĂ©cessitent donc un examen, mais ne sont pas comptabilisĂ©es comme comportement malveillant confirmĂ©.
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-write-feature-docs/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/warpdotdev-write-feature-docs?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/warpdotdev-write-feature-docs?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/warpdotdev-write-feature-docs/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/warpdotdev-write-feature-docs.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). write-feature-docs security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/warpdotdev-write-feature-docs/audits/1@techreport{warpdotdev-warpdotdev-write-feature-docs-2026,
author = {warpdotdev},
title = {write-feature-docs security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/warpdotdev-write-feature-docs/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: "write-feature-docs security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "warpdotdev"
date-released: "2026-09-04"
url: "https://skillstore.io/skills/warpdotdev-write-feature-docs/audits/1"
identifiers:
- type: other
value: "skillstore:warpdotdev-write-feature-docs:audit:1"
description: "Skillstore immutable audit report identifier"
Convert an approved product or technical specification into an accurate first-pass documentation page.
Verify implementation details and isolate only the questions that require subject matter expertise.
Create or update an MDX page and open a structured draft pull request for editorial review.
Draft documentation for Warp feature [name] using spec [ID]. Find PRODUCT.md and TECH.md, then present the content design plan.
Research feature [name] without a spec. Verify behavior in [repository], identify unknowns, and ask only targeted questions before planning the page.
Document [feature] using [spec ID]. Prefer updating [existing page], verify UI paths, then present the content plan and outline separately.
Prepare a draft documentation pull request for [feature]. Verify release readiness, sanitize screenshots, list unverified claims, and include the confirmed content design plan.
Auteur
warpdotdevLicence
MIT
RĂ©vision Skillstore
r1
Avis de version
Lâauteur nâa dĂ©clarĂ© aucune version.
RĂ©f
e5464e662405de6361fdde6b984f9ea865635f64
RĂ©cence de maintenance
08/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.
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.
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.
Créer la documentation des composants FlowGram
par bytedance
Les composants material de FlowGram ont besoin dâune documentation cohĂ©rente, dâexemples Story exĂ©cutables, de tableaux dâAPI et dâĂ©tapes de rĂ©vision bilingues. Cette skill fournit Ă Claude, Codex et Claude Code un workflow structurĂ© pour produire ces ressources.
Rédiger une meilleure documentation avec une revue guidée
par ZhanlinCui
Les documents complexes échouent souvent parce que le contexte, la structure et les hypothÚses des lecteurs ne sont pas clairs. Cette compétence guide Claude, Codex ou Claude Code dans un workflow de coécriture reproductible qui recueille le contexte, rédige des sections et teste la compréhension des lecteurs.
Créer des README centrés sur le public
par softaworks
Les README génériques passent souvent à cÎté des besoins des contributeurs, des coéquipiers ou des futurs mainteneurs. Cette skill guide Claude, Codex et Claude Code au moyen de questions sur le public, de modÚles et de contrÎles qualité.
Générer une documentation de code maintenable
par sickn33
La documentation manuelle prend souvent du retard par rapport au code actif. Cette skill aide Claude, Codex et Claude Code Ă crĂ©er une documentation claire et des plans dâautomatisation.
Planifier des structures de livres pédagogiques
par 92Bilal26
Les grands livres pĂ©dagogiques peuvent devenir incohĂ©rents, surchargĂ©s ou difficiles Ă parcourir. Cette compĂ©tence crĂ©e des plans structurĂ©s avec un enchaĂźnement des chapitres, des dĂ©pendances et des points de contrĂŽle de lâapprentissage.
Créer une documentation technique complÚte
par 89jobrien
Les équipes techniques ont besoin d'une documentation claire pour les API, les versions et les migrations. Cette compétence crée une documentation structurée avec des modÚles et des exemples pratiques.