Skip to content

im-shashanks/claude-plugins / shaktra/skills/shaktra-stories

shaktra-stories

Verified

Story 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.

FileKindSize
SKILL.mdskill md1.5 KB
sprint-schema.mdmarkdown2.2 KB
story-creation.mdmarkdown6.3 KB
story-schema.mdmarkdown5.0 KB
story-tiers.mdmarkdown2.6 KB

sprint-schema.md

View on GitHub
# Sprint Schema

Defines `.shaktra/sprints.yml` — sprint state managed by the scrummaster agent. Only active when `settings.sprints.enabled` is true.

## Schema

```yaml
current_sprint:
  id: string               # "SP-001" — sequential
  goal: string             # business objective for this sprint (PM assigns)
  start_date: string       # ISO 8601 date
  end_date: string         # start_date + settings.sprints.sprint_duration_weeks
  stories: [string]        # story IDs committed to this sprint
  capacity_points: integer # team capacity in story points
  committed_points: integer # sum of committed story points

velocity:
  history:
    - sprint_id: string
      planned_points: integer
      completed_points: integer
  average: number          # rolling average of completed_points
  trend: string            # "improving" | "stable" | "declining"

backlog:
  - story_id: string
    points: integer
    priority: string       # "critical" | "high" | "medium" | "low"
    blocked_by: [string]   # story IDs that must complete first
```

## Velocity Calculation

```
average = sum(history[-3:].completed_points) / min(len(history), 3)

if len(history) >= 3:
    recent = average of last 2 sprints
    older  = history[-3].completed_points
    if recent > older * 1.1: trend = "improving"
    elif recent < older * 0.9: trend = "declining"
    else: trend = "stable"
else:
    trend = "stable"
```

## Backlog Ordering

Scrummaster sorts backlog by: blocked_by (unblocked first) → priority → points (smallest first).

## Template Migration Contract

The init template (`templates/sprints.yml`) uses a simplified structure:

```yaml
current_sprint: null
velocity_history: []
sprints: []
```

On first sprint creation, the scrummaster agent migrates to the target schema:

1. `velocity_history: []` → `velocity.history: []` + `velocity.average: 0` + `velocity.trend: "stable"`
2. `sprints: []` → removed (sprint history lives in `velocity.history`)
3. `current_sprint: null` → populated with first sprint data
4. `backlog: []` → added (empty initially, populated during sprint allocation)

After migration, the file follows this schema exclusively. The scrummaster performs this migration automatically on first sprint creation; no manual intervention required.
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: 472kUpdated Claude CodeCodexUnverifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall