write-tech-spec은(는) 무엇을 하나요?
주요 Warp 기능에 대한 TECH.md 스펙을 작성합니다. 먼저 현재 코드베이스와 구현 제약 사항을 조사한 후, 제품 스펙과 연결된 기술 스펙, 구현 계획, 또는 아키텍처 문서를 생성합니다. 사용자가 이에 해당하는 요청을 할 때 사용하세요.
현재 코드베이스와 구현 제약 사항을 조사한 후, 주요 Warp 기능에 대한 TECH.md 스펙을 작성합니다. 사용자가 제품 스펙과 관련된 기술 스펙, 구현 계획, 또는 아키텍처 문서를 요청할 때 사용합니다.
이 스킬은 사용자가 특정 기능이나 제품 요구 사항에 대한 기술 설계 문서를 요청할 때, Warp 코드베이스를 깊이 탐색하고 관련 제약 조건을 파악한 후 `TECH.md` 형식의 상세한 기술 스펙을 자동 생성합니다. 주로 Warp 터미널 에뮬레이터와 같은 대규모 프로젝트에서 기능 추가나 아키텍처 변경이 필요할 때 유용합니다. 이 스킬은 Rust, TypeScript, Swift 등 다양한 언어로 작성된 Warp의 복잡한 코드베이스를 효과적으로 분석할 수 있다고 가정합니다. 결과물은 문제 정의, 배경, 구현 세부 사항, 실패 모드(Failure Modes) 및 성능 고려 사항을 포함한 종합적인 기술 문서로, 개발자와 팀 간의 의사소통과 설계 리뷰를 지원합니다.
npx skills add https://github.com/warpdotdev/common-skills/tree/main/skills/write-tech-specInstalled? Explore more 연구 & 데이터 분석 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
주요 Warp 기능에 대한 TECH.md 스펙을 작성합니다. 먼저 현재 코드베이스와 구현 제약 사항을 조사한 후, 제품 스펙과 연결된 기술 스펙, 구현 계획, 또는 아키텍처 문서를 생성합니다. 사용자가 이에 해당하는 요청을 할 때 사용하세요.
This repo contains 16 individual skills — each has its own dedicated page.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Drive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keeping both specs updated as implementation evolves. Use when starting a significant feature, planning agent-driven implementation, or when the user wants product and tech specs checked into source control.
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.
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.
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.
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.