jr-add-story

Generate vertical-slice user stories for existing features via contract-first clarification.

3|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/rusi/junior --skill jr-add-story
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jr-add-story
Source: https://github.com/rusi/junior/tree/main/agents/skills/jr-add-story
Command: npx skills add https://github.com/rusi/junior --skill jr-add-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams add well-scoped, vertical-slice user stories to existing features through contract-first clarification and validation.

Core Features & Use Cases

  • Contract-first clarification to validate story scope and requirements
  • Vertical-slice planning that ensures end-to-end integration
  • Generated story files and project tracking updates in the feature docset

Quick Start

Invoke /jr-add-story and complete the clarification loop to add a new story to an existing feature.

Frequently Asked Questions about jr-add-story

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

FAQPage Schema
How do I add well-scoped user stories to existing features?

To add well-scoped user stories to existing features, use a contract-first clarification loop that validates story scope and requirements before generating vertical-slice stories for end-to-end integration.

What is vertical-slice story generation in feature development?

Vertical-slice story generation is a planning approach that ensures new user stories cover end-to-end integration within a feature, validating scope through a structured workflow from contract to generation.

How does contract-first clarification validate story scope?

Contract-first clarification validates story scope by enforcing a structured workflow with steps for scanning, clarification, contract definition, and end-to-end story generation before any code is written.

Can I use contract-first planning for feature enhancement initiatives?

Yes, contract-first planning applies directly to feature enhancement initiatives within codebases where stories are decomposed, validated, and tracked from contract to generation.

What's the best way to decompose and track stories in a feature docset?

The best way to decompose and track stories is through a structured workflow that generates story files and updates project tracking within the feature docset after vertical-slice validation.

Do I need existing features before running story generation?

Yes, this story generation workflow is designed to add new stories to existing features, requiring an established codebase where stories can be decomposed and tracked through contract validation.