rcode-hussain-sm

Prepare sprint planning, story readiness, and status reports for agile teams.

2|1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/hanzlahabib/rcode --skill rcode-hussain-sm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rcode-hussain-sm
Source: https://github.com/hanzlahabib/rcode/tree/main/rcode/skills/agents/hussain-sm
Command: npx skills add https://github.com/hanzlahabib/rcode --skill rcode-hussain-sm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns unclear backlog items into dev-ready stories and keeps sprint execution orderly when priorities, blockers, or scope change. It helps a Scrum Master remove ambiguity before work starts, so the team can move without waiting for extra clarification.

Core Features & Use Cases

  • Sprint Planning: Build a focused sprint goal, validate capacity assumptions, and commit the right stories.
  • Story Preparation: Split vague requests into concrete, independently deliverable stories with acceptance criteria and dependencies.
  • Status Reporting: Summarize story progress, blockers, and ownership in a clear sprint view.
  • Retrospectives and Course Correction: Capture outcomes, assign action items, and handle mid-sprint changes explicitly instead of letting scope drift.
  • Use Case: A product owner asks for a sprint update, a new story, and a retro summary; this Skill prepares each artifact in the correct format and keeps the team aligned.

Quick Start

Ask Hussain to prepare the next story from the backlog or to plan the current sprint with clear capacity, risks, and acceptance criteria.

Frequently Asked Questions about rcode-hussain-sm

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

FAQPage Schema
How do I prepare vague backlog items for sprint planning?

Sprint planning preparation splits vague requests into dev-ready stories by decomposing epics, defining verifiable acceptance criteria, and validating capacity assumptions to commit the right work. This removes ambiguity so teams can execute without waiting for extra clarification.

What is the best way to handle mid-sprint course correction and scope drift?

Mid-sprint course correction handles priority and blocker changes explicitly through scope tradeoff decisions and blocker escalation. This prevents uncontrolled scope drift by capturing outcomes and assigning owned action items instead of letting priorities slip silently.

How do I run an agile retrospective that captures clear action items?

Agile retrospectives capture sprint outcomes and assign explicitly owned action items to drive continuous improvement. This ensures accountability and prevents past mistakes from recurring by documenting verifiable next steps for the delivery team.

Can I use this Skill to generate a sprint status report for a product owner?

Yes, sprint status reporting summarizes story progress, blockers, and ownership in a clear sprint view. This provides product owners with a structured artifact detailing current execution state and dev-ready story preparation.

Does this Skill work for Scrum Master workflows like backlog grooming and standup facilitation?

Yes, it applies directly to Scrum Master workflows including backlog grooming, epic review, standup facilitation, and sprint goal definition. It requires explicit capacity checks and story decomposition to keep execution dev-ready and unambiguous.

Why does sprint planning fail when stories lack acceptance criteria?

Sprint planning fails without verifiable acceptance criteria because stories remain ambiguous and block dev-ready execution. Enforcing story decomposition and dependency identification removes this ambiguity before work starts.