im-shashanks/claude-plugins / shaktra/skills/shaktra-stories
shaktra-stories
VerifiedStory creation, enrichment, and related schemas. Defines HOW to create and validate user stories, WHAT fields exist per tier (story-schema), WHICH tier a story belongs to (story-tiers), and sprint state format (sprint-schema). Loaded by scrummaster and other story-consuming agents.
Shaktra Stories — Creation, Enrichment & Story Schemas
This skill defines story creation processes and contains the canonical schemas for stories, tiers, and sprints.
Sub-Files
| File | Purpose |
|---|---|
story-creation.md | Creation process (7 steps), enrichment process (6 steps), validation rules, Final Verification Loop |
story-schema.md | Tier-aware story YAML — field definitions per tier (source of truth for story structure) |
story-tiers.md | 4-tier story classification with detection logic and gates |
sprint-schema.md | Sprint state — velocity tracking, backlog, capacity |
How Agents Use This Skill
The scrummaster loads this skill and follows the processes in story-creation.md:
- Create mode: Design doc in → stories out. Follows the 7-step creation process.
- Enrich mode: Sparse stories in → enriched stories out. Follows the 6-step enrichment process.
- Sprint allocation: Uses
sprint-schema.mdfor sprint state format.
Other agents (tpm-quality, product-manager, developer, sw-engineer, bug-diagnostician) load this skill to access story-schema.md and story-tiers.md for reading and reviewing stories.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |