technical-stories

Create and manage technical stories with subtasks and dev-tracking timelines.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/diegoknsk/video-processing-engine-video-management-lambda --skill technical-stories
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: technical-stories
Source: https://github.com/diegoknsk/video-processing-engine-video-management-lambda/tree/main/.cursor/skills/technical-stories
Command: npx skills add https://github.com/diegoknsk/video-processing-engine-video-management-lambda --skill technical-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes how technical stories are created and tracked in a software project, ensuring consistent structure and auditable progress across teams.

Core Features & Use Cases

  • Enforced folder and file structure: all stories live under storys/<Storie-XX-Name>/ with a story.md and a subtask/ directory for task breakdown.
  • Dev tracking across Brasília time: records start and end times, computes total development duration, and maintains a clear progress timeline.
  • Subtask management and traceability: supports multiple subtasks with explicit acceptance criteria to enable progress reporting and quality checks.

Quick Start

Create a new technical story by ensuring a storys/ folder exists, create storys/Storie-XX-Description/ with story.md and a subtask/ directory, and start the dev-tracking timeline.

Frequently Asked Questions about technical-stories

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

FAQPage Schema
How do I create technical stories with a standardized folder structure?▼

To create technical stories, set up a storys/ folder, then create storys/Storie-XX-Description/ containing a story.md file and a subtask/ directory. This enforces consistent folder structure for story creation and auditable progress tracking across teams.

How does dev tracking work for technical stories?▼

Dev tracking records start and end times for technical stories to compute total development duration. It maintains a clear progress timeline aligned to Brasília time, ensuring standardized time-zone tracking across your project lifecycle.

What is the best way to manage subtasks and acceptance criteria for development tracking?▼

The best way to manage subtasks is placing them in the subtask/ directory within each story folder. This supports multiple subtasks with explicit acceptance criteria, enabling accurate progress reporting and quality checks for technical stories.

Do I need any specific dependencies to use this technical story management workflow?▼

No specific dependencies are required to use this technical story management workflow. You only need to ensure a storys/ folder exists in your project to start creating stories, subtasks, and dev-tracking timelines.

Why should I standardize technical story creation across my software project?▼

Standardizing technical story creation ensures consistent structure and auditable progress across teams. It enforces mandatory folder structures, time-zone aligned tracking, and clear acceptance criteria for each subtask to maintain quality and traceability.