skills.rest
codysumpter-cloud
codysumpter-cloudCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

create-tech-spec

Translate product specs and GitHub issues into technical plans with code paths and risks.

2|2|Updated Mar 20, 2026
Search Tags:#implementation planning#product specification#tech spec#GitHub issues#BMO projects
One-click install
npx skills add https://github.com/codysumpter-cloud/buddy-brain --skill create-tech-spec-codysumpter-cloud
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-tech-spec
Source: https://github.com/codysumpter-cloud/buddy-brain/tree/main/.agents/skills/create-tech-spec
Command: npx skills add https://github.com/codysumpter-cloud/buddy-brain --skill create-tech-spec-codysumpter-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The creation of technical specifications for BMO projects can be time-consuming and error-prone, especially when translating product intent into actionable implementation plans.

Core Features & Use Cases

  • Product to Implementation Translation: Translates high-level product specifications into detailed technical plans.
  • Issue and Request Handling: Integrates with product specs, GitHub issues, and operator requests to gather necessary context.
  • Technical Spec Generation: Generates specs/GH<number>/tech.md files with structured content, including problem statements, code paths, risks, and rollback plans.

Quick Start

To create a tech spec for a project, run the create-tech-spec skill and provide the relevant GitHub issue number.

Frequently Asked Questions about create-tech-spec

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

FAQPage Schema
How do I create a tech spec from a GitHub issue for BMO projects?▼

It translates product specifications, GitHub issue details, and operator requests into comprehensive technical plans. This ensures accurate implementation planning by analyzing code paths and assessing risks for BMO projects.

What is included in a generated technical specification plan?▼

A generated technical specification includes structured content with problem statements, analyzed code paths, risk assessments, and rollback plans. It translates high-level product intent into actionable implementation details.

Can I use operator requests and product specs to generate implementation plans?▼

Yes, you can use operator requests and product specs to generate implementation plans. The skill integrates these inputs to ensure accurate technical spec creation and comprehensive implementation planning for your project.

Do I need to provide a GitHub issue number to generate a tech spec?▼

Yes, you need to provide a relevant GitHub issue number to generate a tech spec. The skill uses this issue number to gather the necessary context and translate product specifications into a detailed technical plan.

Why does implementation planning for BMO projects require risk assessment and rollback plans?▼

Implementation planning requires risk assessment and rollback plans to prevent errors during product-to-implementation translation. Generating technical specs with these elements ensures accurate code path analysis and safe deployment for BMO projects.

Related Skills

Explore More Software Engineering Skills→
unblockedunblocked
13

enrich-ticket

Enrich issue tracker tickets with organizational context and cited findings.

Official
Advanced
kkestellkkestell
1

kwork

Execute repository implementation plans with code changes, tests, and reviews.

Community
Advanced
Steve-Smith-CODESteve-Smith-CODE

speckit-taskstoissues

Convert local task lists into GitHub issues with duplicate detection.

Community
Advanced
thomfilgthomfilg

spec

Generate technical specifications from product briefs and codebase analysis.

Community
Intermediate