What is the INVEST criteria used by this skill?

The skill ensures every ticket is Independent, Negotiable, Valuable, Estimable, Small, and Testable to maximize team velocity and reduce ambiguity.

How does this skill help prevent scope creep?

It explicitly defines both 'In Scope' and 'Out of Scope' boundaries for every ticket, ensuring engineers focus only on the required deliverables.

Can it handle complex frontend and backend dependencies?

Yes, it utilizes vertical slicing patterns to ensure each ticket delivers a testable piece of value, avoiding the pitfalls of horizontal FE/BE splits.

Is the output compatible with Jira or GitHub Issues?

Absolutely. The skill generates clean Markdown that can be easily copied into Jira, Linear, GitHub Issues, or any other project management tool.

Tech Story Architect

Name: Tech Story Architect
Author: chavangorakh1999

bychavangorakh1999

0•

Productividad y Flujo de Trabajo

Breaks down complex epics into high-quality, INVEST-ready technical tickets with clear scope and acceptance criteria.

The Tech Story Architect skill transforms high-level feature requests and large epics into actionable, granular technical stories optimized for engineering teams. By applying the INVEST framework (Independent, Negotiable, Valuable, Estimable, Small, Testable), it helps prevent scope creep and reduces estimation variance. It provides standardized templates that include technical implementation approaches, explicit 'out-of-scope' boundaries, and rigorous definitions of done, making it an essential tool for lead engineers and product managers during sprint planning or backlog refinement.

Características Principales

01Dependency mapping and identification of parallelization opportunities

02Automated EPIC breakdown using vertical slicing and technical enablers

03INVEST criteria validation to ensure ticket quality and estimability

04Advanced story splitting patterns for complex workflows and data migrations

05Standardized technical templates with Scope, Approach, and Acceptance Criteria

060 GitHub stars

Casos de Uso

01Defining clear technical boundaries and 'Definition of Done' for complex features

02Splitting monolithic tasks into small, testable tickets during sprint planning

03Converting a product requirement document (PRD) into a technical backlog

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add chavangorakh1999/sde-skills tech-stories

For use in Claude.ai and ChatGPT

Características Principales

01Dependency mapping and identification of parallelization opportunities

02Automated EPIC breakdown using vertical slicing and technical enablers

03INVEST criteria validation to ensure ticket quality and estimability

04Advanced story splitting patterns for complex workflows and data migrations

05Standardized technical templates with Scope, Approach, and Acceptance Criteria

060 GitHub stars

Casos de Uso

01Defining clear technical boundaries and 'Definition of Done' for complex features

02Splitting monolithic tasks into small, testable tickets during sprint planning

03Converting a product requirement document (PRD) into a technical backlog