Skip to content

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

shaktra-reference

Verified

Shared constants, quality standards, and state schemas for all Shaktra agents. Defines severity taxonomy, quality principles, guard tokens, review dimensions, and YAML schemas.

schemas/analysis-manifest-schema.md

View on GitHub
# Analysis Manifest Schema

Defines `.shaktra/analysis/manifest.yml` — the checkpoint file that tracks analysis progress for resumability. Managed by `/shaktra:analyze`; initialized by `/shaktra:init`.

## Schema

```yaml
version: string             # analysis version identifier
started_at: datetime | null  # ISO 8601 timestamp when analysis began
completed_at: datetime | null # ISO 8601 when all stages finished
status: string              # "pending" | "in_progress" | "complete" | "partial"
execution_mode: string      # "standard" | "deep"

stages:
  pre_analysis:
    static:
      status: string        # "pending" | "complete"
      completed_at: datetime | null
    overview:
      status: string        # "pending" | "complete"
      completed_at: datetime | null

  dimensions:
    D1..D9:                  # one entry per analysis dimension
      name: string           # human-readable dimension name
      status: string         # "pending" | "in_progress" | "complete" | "failed"
      output_file: string    # filename for dimension output (e.g., "structure.yml")
      started_at: datetime | null
      completed_at: datetime | null
      error: string | null   # error message if status is "failed"

  finalize:
    validation:
      status: string        # "pending" | "complete"
    checksums:
      status: string        # "pending" | "complete"
    diagrams:
      status: string        # "pending" | "complete"
    memory:
      status: string        # "pending" | "complete"
```

## Dimensions

| Key | Name | Output File |
|---|---|---|
| D1 | Architecture & Structure | `structure.yml` |
| D2 | Domain Model & Business Rules | `domain-model.yml` |
| D3 | Entry Points & Interfaces | `entry-points.yml` |
| D4 | Coding Practices & Conventions | `practices.yml` |
| D5 | Dependencies & Tech Stack | `dependencies.yml` |
| D6 | Technical Debt & Security | `tech-debt.yml` |
| D7 | Data Flows & Integration | `data-flows.yml` |
| D8 | Critical Paths & Risk | `critical-paths.yml` |
| D9 | Git Intelligence | `git-intelligence.yml` |

## Status Transitions

**Top-level status:**
- `pending` -> `in_progress` (first dimension starts)
- `in_progress` -> `complete` (all dimensions + finalize stages complete)
- `in_progress` -> `partial` (some dimensions complete, others failed or pending at session end)

**Dimension status:**
- `pending` -> `in_progress` (analyzer agent starts dimension)
- `in_progress` -> `complete` (output file written and valid)
- `in_progress` -> `failed` (error captured in `error` field)

## Consumer Reference

| Consumer | Usage |
|---|---|
| `/shaktra:analyze` | Reads to resume interrupted analysis; writes to update progress |
| `/shaktra:init` | Creates from template with all stages set to `pending` |
| `/shaktra:doctor` | Reads to report analysis health status |
| `cba-analyzer` agent | Reads assigned dimension; writes status on completion |
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 CodeCodexVerifiedInstall
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