im-shashanks/claude-plugins / shaktra/skills/shaktra-reference
shaktra-reference
VerifiedShared constants, quality standards, and state schemas for all Shaktra agents. Defines severity taxonomy, quality principles, guard tokens, review dimensions, and YAML schemas.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.0 KB |
| guard-tokens.md | markdown | 3.0 KB |
| quality-dimensions.md | markdown | 4.0 KB |
| quality-principles.md | markdown | 3.9 KB |
| schemas/analysis-manifest-schema.md | markdown | 2.8 KB |
| schemas/anti-patterns-schema.md | markdown | 1.6 KB |
| schemas/briefing-schema.md | markdown | 2.9 KB |
| schemas/design-doc-schema.md | markdown | 4.9 KB |
| schemas/handoff-schema.md | markdown | 4.2 KB |
| schemas/journey-schema.md | markdown | 3.4 KB |
| schemas/observations-schema.md | markdown | 1.7 KB |
| schemas/persona-schema.md | markdown | 2.8 KB |
| schemas/prd-schema.md | markdown | 3.3 KB |
| schemas/principles-schema.md | markdown | 2.3 KB |
| schemas/procedures-schema.md | markdown | 1.7 KB |
| schemas/refactoring-handoff-schema.md | markdown | 2.4 KB |
| schemas/research-schema.md | markdown | 3.7 KB |
| schemas/settings-schema.md | markdown | 7.7 KB |
| severity-taxonomy.md | markdown | 3.2 KB |
schemas/handoff-schema.md
View on GitHub# Handoff Schema
Defines `.shaktra/stories/<story_id>/handoff.yml` — the TDD state machine that tracks a story through plan → tests → code → quality → complete.
## Identity
```yaml
story_id: string # matches story file id
tier: string # "trivial" | "small" | "medium" | "large"
current_phase: string # "pending" | "plan" | "tests" | "code" | "quality" | "complete" | "failed"
completed_phases: [string] # append-only log of completed phases
```
## Plan Summary
```yaml
plan_summary:
components:
- name: string
file: string
responsibility: string # single sentence, SRP
test_plan:
test_count: integer
test_types: [string] # "unit" | "integration" | "contract"
mocks_needed: [string]
edge_cases: [string]
implementation_order: [string] # file paths, minimal-dependency order
patterns_applied:
- pattern: string # design pattern, architectural pattern, or quality principle name
location: string # file or component where applied
guidance: string # actionable implementation instruction
source: string # "decision" | "analysis" | "principle" | "design-doc"
scope_risks:
- risk: string # what could go wrong
likelihood: string # "low" | "medium" | "high"
prevention: string # how the plan mitigates it
```
## Test Summary
```yaml
test_summary:
all_tests_red: boolean # must be true before advancing
test_count: integer
test_files: [string]
```
## Code Summary
```yaml
code_summary:
all_tests_green: boolean # must be true before advancing
coverage: integer # percentage — checked against tier threshold
files_modified: [string]
deviations: # plan deviations — empty list if none
- change: string # what diverged from the plan
justification: string # why the deviation was necessary
```
## Observations Path
```yaml
observations_path: string # optional — path to .observations.yml in the story directory
```
Agents write observations during workflow execution. The memory-curator reads observations from this path during the MEMORY phase.
## Quality Findings
**Population:** The orchestrator persists findings to this field after each quality gate (QUICK_CHECK and COMPREHENSIVE). SW Quality returns findings as output; the orchestrator writes the latest findings here. The `check_p0_findings` hook reads this field at workflow completion — it filters out findings with `resolved: true`.
**Note:** SW Quality agent output may include additional fields (`check_id`, `evidence`, `guidance`) beyond the schema below. The orchestrator writes the full agent output; consumers should tolerate extra fields.
```yaml
quality_findings:
- severity: string # P0 | P1 | P2 | P3
dimension: string # quality dimension (A-M)
gate: string # "plan" | "test" | "code" | "quality" — which gate produced this
issue: string # specific description of the finding
file: string
line: integer
resolved: boolean # true if fixed in a subsequent fix loop
```
## Memory Guard
```yaml
memory_captured: boolean # default: false — must be true before completion
```
## Phase Transitions
| From | To | Guard |
|---|---|---|
| plan | tests | `plan_summary` is populated; `test_plan.test_count > 0` (skip for Trivial) |
| tests | code | `test_summary.all_tests_red == true` (skip for Trivial) |
| code | quality | `code_summary.all_tests_green == true`; coverage ≥ tier threshold from `settings.tdd` |
| quality | complete | No P0 findings; P1 count ≤ `settings.quality.p1_threshold`; `memory_captured == true` |
| _any_ | failed | Unrecoverable error or user abort |
## Validation Rules
1. `current_phase` must be one of the 7 allowed values.
2. `completed_phases` must be a prefix of [plan, tests, code, quality] — phases cannot be skipped.
3. `tier` must match the story file's tier.
4. `test_summary.test_count` must match `plan_summary.test_plan.test_count` (or include a variance note).
5. `coverage` is checked against `settings.tdd.coverage_threshold` or `settings.tdd.hotfix_coverage_threshold` depending on tier.
6. `memory_captured` must be `true` before transitioning to `complete`.
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: 472k | 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 |