📦

write-tech-spec

Name: write-tech-spec
Author: warpdotdev

مراجعة المحتوى 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 برونزي

التثبيت باستخدام Agent لدي

انسخ هذا الطلب إلى Agent لديك. يتضمن صفحة Skill المعتمدة وملف manifest.

طلب الوكيل

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.

يجب أن يواصل Agent عرض خطته وطلب أي تأكيد تفرضه سياسة الأمان.

موارد مهيّأة لـ Agents

استخدم هذه الروابط عندما يحتاج AI Agent أو crawler أو script إلى سياق نظيف بدلًا من قراءة الصفحة كاملة.

تفاصيل Markdown GET /skills/warpdotdev-write-tech-spec.md manifest موقَّع GET /api/skills/warpdotdev-write-tech-spec/manifest lockfile موقَّع GET /api/skills/warpdotdev-write-tech-spec/lockfile

اختبرها

جارٍ استخدام "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.

التدقيق الأمني

آمن

v1 • ١٨‏/٩‏/٢٠٢٦ فتح التقرير المرتبط بالإصدار

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.

الملفات التي تم فحصها

الأسطر التي تم تحليلها

عناصر المراجعة

تم تجاهل الإيجابيات الكاذبة

عوامل الخطر

⚙️ الأوامر الخارجية (22)

🌐 الوصول إلى الشبكة (2)

SKILL.md:40 SKILL.md:41

لم يكتشف أحدث تدقيق ثابت ودلالي مكتمل أي نتائج أمنية مؤكدة. ولا يثبت ذلك أن المهارة خالية من الآثار الجانبية.

دقّقه: codex

شارك واستشهد بهذا التقرير

شارك تقرير التقييم المرتبط بالإصدار والشارة المحايدة وبطاقة التضمين والاستشهادات. تعرض Skillstore الأدلة من دون أن تقرر ما إذا كانت هذه المهارة آمنة.

فتح التقرير المرتبط بالإصدار

نسخ رابط التقرير

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

سبب هذا التقييم موثوقية الأدلة: متوسط

الهندسة المعمارية

قابلية الصيانة

المحتوى

المجتمع

الامتثال للمواصفات

ما الذي يمكنك بناؤه

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

تنبيه الإصدار

لم يعلن المؤلف عن إصدار.

المستودع

https://github.com/warpdotdev/common-skills/tree/69b4753651ab7fab518c82be087b9f1d5b966631/.agents/skills/write-tech-spec

مرجع

0b0c8bd4f7023650f59eae864e7456d5a43fac55

حداثة الصيانة

١٨‏/٩‏/٢٠٢٦

الاستخدام

0 تنزيلات · 0 مشاهدات

بنية الملفات

📄 SKILL.md