skills.rest
humansys
humansysOFFICIAL
Explore all skills by this author →
WebsiteGitHub

rai-story-start

Create a story branch and scope commit from a development branch.

71|8|Updated Feb 13, 2026
Search Tags:#git#commit#story#branching#backlog#scope#rai
One-click install
npx skills add https://github.com/humansys/raise --skill rai-story-start-humansys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rai-story-start
Source: https://github.com/humansys/raise/tree/main/packages/raise-cli/src/raise_cli/skills_base/rai-story-start
Command: npx skills add https://github.com/humansys/raise --skill rai-story-start-humansys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a repeatable, governed way to start story work by creating a dedicated story branch and a scope commit that documents boundaries and done criteria so development begins with clear intent and traceability.

Core Features & Use Cases

  • Branch creation: always creates a story/ branch from the configured development branch to enforce consistent branching.
  • Scope documentation: scaffolds a user story file and a scope file capturing in-scope/out-of-scope items and observable done criteria, then commits them with a standardized message.
  • Backlog integration: optionally transitions a backlog ticket to in_progress via configured adapters as a best-effort, non-blocking step.
  • Use case: starting a new story from an epic or backlog item where clear scope, branch isolation, and an audit-friendly commit are required.

Quick Start

Create a story branch from the development branch, add the story and scope markdown files under the epic, commit the scope with a clear "Done when" section, and show the branch name and commit hash.

Frequently Asked Questions about rai-story-start

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

FAQPage Schema
How do I create a git story branch and document scope for a new backlog item?▼

A scope commit documents the boundaries and observable done criteria for a story branch before development begins. It scaffolds a user story file and scope file, then commits them with a standardized message to provide audit-friendly traceability for backlog or epic work.

What's the best way to enforce consistent branching when starting new epic stories?▼

Yes, backlog ticket transitions are supported optionally via configured adapters. When starting a story branch, the Skill can transition a backlog ticket to in_progress as a best-effort, non-blocking step, ensuring the project management system stays synchronized without halting the branch creation process.

Can I transition a backlog ticket to in_progress when creating a story branch?▼

To create a story branch, this Skill initializes a dedicated branch from the configured development branch, scaffolds a user story file, and commits a scope document capturing in-scope, out-of-scope, and done criteria. It ensures development starts with clear intent and traceability.

Do I need a .raise/manifest.yaml file to initialize story branches?▼

Yes, a .raise/manifest.yaml file is required because the Skill reads branch configuration from it to determine the base development branch and locate configured backlog adapters. Without this manifest, the Skill cannot enforce consistent branching or perform optional ticket transitions.

What should be included in a scope commit for a new story branch?▼

A scope commit should include a user story file and a scope file capturing in-scope and out-of-scope items alongside observable done criteria. This Skill scaffolds these files under the epic directory and commits them with a standardized message to record clear development boundaries.

Related Skills

Explore More Software Engineering Skills→
taiga-Ktaiga-K
1

create-branch

Create GitFlow feature, release, and hotfix branches with validated naming.

Community
Intermediate
haabehaabe

definition-of-done

Verify that a feature or story meets its Definition of Done criteria.

Community
Advanced
GDSDNGDSDN
3

po-close-story

Close product development stories by updating status, changelog, and epic indexes.

Community
Advanced
mhattingpetemhattingpete
657

git-pushing

Stage, commit, and push code changes with conventional commit messages.

Community
Basic