tech-stories

Generates INVEST-ready project tasks from epics with context, criteria, and scope.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/chavangorakh1999/sde-skills --skill tech-stories
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-stories
Source: https://github.com/chavangorakh1999/sde-skills/tree/main/sde-execution/skills/tech-stories
Command: npx skills add https://github.com/chavangorakh1999/sde-skills --skill tech-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps break down large epics or features into smaller, manageable, and well-defined technical tickets that adhere to the INVEST criteria, improving sprint planning and development clarity.

Core Features & Use Cases

  • INVEST Criteria Enforcement: Ensures tickets are Independent, Negotiable, Valuable, Estimable, Small, and Testable.
  • Structured Ticket Generation: Provides a template for creating clear technical tickets including context, scope, acceptance criteria, and definition of done.
  • Epic Splitting Guidance: Offers patterns and strategies for effectively splitting large pieces of work into smaller, actionable items.
  • Use Case: When faced with a large feature like "Implement user profile management," this Skill can help break it down into tickets for "Create user profile database schema," "Build user profile API endpoints," "Develop user profile frontend form," and "Add profile picture upload functionality."

Quick Start

Use the tech-stories skill to break down the epic "Implement real-time chat functionality".

Frequently Asked Questions about tech-stories

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

FAQPage Schema
How do I break epics into INVEST-ready tickets for agile sprint planning?

To break epics into INVEST-ready tickets, you define each ticket's context, scope, technical approach, acceptance criteria, and definition of done. This ensures tickets are Independent, Negotiable, Valuable, Estimable, Small, and Testable for sprint planning.

What are the best strategies for splitting large user stories in agile?

Effective story splitting strategies include dividing large pieces of work by workflow, data complexity, or performance tiers. This approach reduces estimation variance and creates smaller, actionable tickets that adhere to INVEST criteria.

What is the INVEST criteria for writing technical tickets in software engineering?

The INVEST criteria for writing technical tickets ensures each item is Independent, Negotiable, Valuable, Estimable, Small, and Testable. This structure provides development clarity and reduces estimation variance for agile teams.

How do I structure technical tickets to include acceptance criteria and definition of done?

To structure technical tickets, use a template that explicitly defines context, scope, technical approach, acceptance criteria, and definition of done. This structured generation ensures development clarity and proper epic breakdown.

Can I use story splitting patterns for complex features like user profile management?

Yes, story splitting patterns handle complex features by breaking them into actionable tickets like creating database schemas, building API endpoints, developing frontend forms, and adding specific functionality, ensuring each piece meets INVEST criteria.

Does breaking down epics reduce estimation variance during sprint planning?

Breaking down epics into well-defined technical tickets does reduce estimation variance during sprint planning. By enforcing INVEST criteria and providing structured ticket generation, teams achieve clearer development scope and more accurate estimations.