Навыки write-tech-spec
📦

write-tech-spec

Ревизия содержимого r1 Безопасно ⚙️ Внешние команды🌐 Доступ к сети

Write Grounded Technical Specs

Technical plans often drift from product intent or the current codebase. This skill researches repository structure and turns constraints into an actionable TECH.md implementation plan.

Поддерживает: Claude Codex Code(CC)
🥉 77 Бронза

Установить с помощью моего Агента

Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.

Запрос агента
Review the Skillstore skill "write-tech-spec" from https://skillstore.io/skills/warpdotdev-write-tech-spec.md and its manifest at https://skillstore.io/api/skills/warpdotdev-write-tech-spec/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.

Ресурсы для AI-агентов

Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.

Протестировать

Использование «write-tech-spec». A product specification for vertical tab hover behavior in an existing desktop application.

Ожидаемый результат:

A TECH.md plan covering current workspace state, affected modules, proposed event handling, testing steps, and commit-pinned code references.

Использование «write-tech-spec». A multi-module feature with uncertain implementation ownership.

Ожидаемый результат:

  • A context section that identifies relevant files and data flow.
  • A proposed changes section that assigns ownership and explains tradeoffs.
  • A validation plan linked to the product behavior.

Использование «write-tech-spec». A large feature with independent frontend and backend work.

Ожидаемый результат:

A coordination plan that explains parallel worktrees, branch strategy, synchronization points, and sequential integration checks.

Аудит безопасности

Безопасно

All 27 static detections are false positives caused by Markdown backticks, documentation URLs, or planning language in SKILL.md. The file describes how to write and validate technical specifications; it contains no executable command, network request, or prompt-injection instruction.

1
Просканировано файлов
96
Проанализировано строк
0
Пункты проверки
0
Ложные срабатывания проигнорированы
Последний завершенный статический и семантический аудит не обнаружил подтвержденных проблем безопасности. Это не доказывает отсутствие побочных эффектов у навыка.
Аудитор:: codex
Поделиться и цитировать этот отчет

Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.

Открыть версионный отчет
Оценка безопасности

Копировать ссылку на отчёт

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

Значок Markdown

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

Значок HTML

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

Встраиваемая карточка

<iframe src="https://skillstore.io/embed/skills/warpdotdev-write-tech-spec.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). write-tech-spec security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/warpdotdev-write-tech-spec/audits/1

Цитата BibTeX

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

Оценка Skillstore

Почему такая оценка Достоверность доказательств: Средний
55
Архитектура
85
Сопровождаемость
87
Контент
65
Сообщество
83
Соответствие спецификации

Что вы можете построить

Plan a multi-module feature

Translate an approved product concept into a scoped technical plan with affected modules, data flow, ownership, and tradeoffs.

Prepare work for implementation

Give an implementation agent a repository-grounded sequence of changes and concrete validation steps.

Align reviewers before coding

Document architecture decisions, risks, testing responsibilities, and optional parallel work before a large change begins.

Попробуйте эти промпты

Start a basic specification
Read the relevant product specification and repository files. Draft a concise TECH.md with Context, Proposed changes, and Testing and validation.
Ground the plan in code
Inspect the current code for this feature, identify the main files, types, data flow, and ownership boundaries, then update the TECH.md plan with precise references.
Add validation coverage
Review this technical specification against the product behavior. Add concrete unit, integration, manual, or visual validation steps for every important behavior invariant.
Design coordinated execution
Evaluate whether parallel sub-agents reduce delivery time for this feature. If useful, define worktrees, branches, ownership boundaries, merge points, and validation ownership in the TECH.md.

Лучшие практики

  • Read the product specification and relevant code before proposing architecture.
  • Use commit-pinned references for important code locations.
  • Map every important product behavior to a concrete validation step.

Избегать

  • Do not guess about repository architecture when the code can be inspected.
  • Do not restate product behavior instead of linking the source specification.
  • Do not propose parallel agents without explicit ownership, worktree, and merge boundaries.

Часто задаваемые вопросы

What does this skill create?
It creates a repository-grounded TECH.md implementation specification for a significant Warp feature.
Does it implement the feature?
No. It documents the implementation plan, architecture, tradeoffs, and validation approach.
Does it require a PRODUCT.md file?
A PRODUCT.md file is preferred because it anchors user-visible behavior, but the skill can work from available requirements.
What repository information does it inspect?
It examines relevant files, types, data flow, ownership boundaries, and the current commit when references are needed.
When should I use the parallelization section?
Use it for large features where independent workstreams can reduce delivery time and have clear coordination boundaries.
Can it create Linear or GitHub issues?
Only after explicit user approval. Ticket creation is optional and should use the appropriate connected tool.

Сведения для разработчиков

Автор

warpdotdev

Лицензия

MIT

Ревизия Skillstore

r1

Примечание о версии

Автор не указал версию.

Ссылка

0b0c8bd4f7023650f59eae864e7456d5a43fac55

Актуальность поддержки

18.09.2026

Использование

0 загрузок · 0 просмотров

Структура файлов

📄 SKILL.md