skills.rest
warpdotdev
warpdotdevOFFICIAL
Explore all skills by this author →
WebsiteGitHub

create-tech-spec

Generate a structured tech spec from a GitHub issue into specs/GH<issue-number>/tech.md.

292|39|Updated Mar 17, 2026
Search Tags:#automation#workflow#tech-spec#spec-generation#github-issues#local-workflow
One-click install
npx skills add https://github.com/warpdotdev/oz-for-oss --skill create-tech-spec-warpdotdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-tech-spec
Source: https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/create-tech-spec
Command: npx skills add https://github.com/warpdotdev/oz-for-oss --skill create-tech-spec-warpdotdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a technical spec from a GitHub issue in this repository by applying the local shared write-tech-spec workflow with Oz-specific issue context and output paths. Use when an issue should be turned into a tech spec artifact stored under specs/GH<issue-number>/tech.md and the agent should prepare file changes only, without creating commits or pull requests itself unless a cloud workflow explicitly asks for it.

Core Features & Use Cases

  • Thin wrapper around the local shared tech-spec workflow: read issue details and produce a tech spec aligned to the repository's conventions.
  • Outputs the tech spec at specs/GH<issue-number>/tech.md and prepares limited repo changes, avoiding automatic PRs or commits unless directed.
  • Optional support for generating a PR metadata file (pr-metadata.json) if a cloud workflow requires it.

Quick Start

Turn a GitHub issue into a tech spec stored at specs/GH<issue-number>/tech.md using the local shared write-tech-spec workflow.

Frequently Asked Questions about create-tech-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a tech spec from a GitHub issue in my repository?▼

This workflow generates a tech spec from a GitHub issue by grounding the issue context in your repository's codebase and existing tooling. It outputs the structured document directly to specs/GH<issue-number>/tech.md.

Does generating technical specs locally create automatic commits or pull requests?▼

Local tech spec generation prepares file changes only and avoids creating commits or pull requests automatically. It enforces a file-change-only scope unless a cloud workflow explicitly requests commits or PR metadata.

What is the standard file path for storing generated tech spec documents?▼

The standard file path for storing generated tech spec documents is specs/GH<issue-number>/tech.md. This path structure aligns with the local write-tech-spec workflow to keep issue documentation organized.

Can I include validation, risks, and follow-ups when converting issues to tech specs?▼

Yes, converting issues to tech specs explicitly documents validation steps, potential risks, and follow-ups alongside the proposed file changes. This ensures the generated tech spec captures comprehensive implementation requirements.

Do I need a cloud workflow to output a pr-metadata.json file for my tech spec?▼

You only need a cloud workflow to output a pr-metadata.json file if your downstream automation explicitly requires it. The default local workflow generates the tech spec and file changes without needing a cloud workflow.

Related Skills

Explore More Software Engineering Skills→
dyoshikawadyoshikawa
1

post-issue-comment

Generate and submit GitHub issue comments using the GitHub CLI.

Community
Intermediate
mikanfactorymikanfactory

commit-and-pr

Commit code changes and create pull requests with Japanese titles.

Community
Advanced
MrlykMrlyk
4

spec-discover

Scan project codebases and propose spec updates under .superharness/spec/.

Community
Intermediate
Terry-MaoTerry-Mao
144

create-tech-spec

Generate technical specifications from GitHub issues using the write-tech-spec workflow.

Community
Intermediate