Skip to content

smorky850612/Aurakit / skills/aura

All-in-one fullstack dev engine. /aura: 46 modes (build/fix/clean/deploy/review/spec/lore/ax/experiment/payment/debug/qa/orchestrate/escalate+), 6-layer security with 32 hooks, tiered models (ZERO/ECO/PRO/MAX), 8 languages, 16 specialized agents, SPEC/EARS/TRUST5/XLOOP/RALF/Autopus absorbed. ~55% token savings.

FileKindSize
SKILL.mdskill md29.2 KB
resources/agent-security.mdmarkdown4.2 KB
resources/agent-spawning.mdmarkdown5.9 KB
resources/agent-team.mdmarkdown5.7 KB
resources/archive-pipeline.mdmarkdown3.5 KB
resources/autopus-agent-teams.mdmarkdown6.8 KB
resources/autopus-ax-annotation.mdmarkdown6.1 KB
resources/autopus-executor-profiles.mdmarkdown9.9 KB
resources/autopus-experiment-loop.mdmarkdown5.9 KB
resources/autopus-lore-commit.mdmarkdown6.0 KB
resources/autopus-pipeline-v2.mdmarkdown8.5 KB
resources/autopus-spec-system.mdmarkdown4.8 KB
resources/autopus-validator-gates.mdmarkdown7.0 KB
resources/autopus-worktree-isolation.mdmarkdown4.6 KB
resources/baas-pipeline.mdmarkdown3.8 KB
resources/batch-pipeline.mdmarkdown4.9 KB
resources/brainstorming.mdmarkdown4.7 KB
resources/branch-finishing.mdmarkdown4.7 KB
resources/build-pipeline.mdmarkdown12.0 KB
resources/build-resolvers-cpp.mdmarkdown10.0 KB
resources/build-resolvers-go.mdmarkdown1.2 KB
resources/build-resolvers-java.mdmarkdown9.1 KB
resources/build-resolvers-kotlin.mdmarkdown8.7 KB
resources/build-resolvers-python.mdmarkdown9.0 KB
resources/build-resolvers-rust.mdmarkdown1.2 KB
resources/build-resolvers-swift.mdmarkdown11.9 KB
resources/build-resolvers.mdmarkdown1.6 KB
resources/business-skills.mdmarkdown7.0 KB
resources/cache-engineering.mdmarkdown6.6 KB
resources/clean-pipeline.mdmarkdown6.5 KB
resources/common-protocol.mdmarkdown7.4 KB
resources/config-schema.mdmarkdown3.0 KB
resources/cross-harness.mdmarkdown16.6 KB
resources/deploy-enterprise.mdmarkdown9.0 KB
resources/deploy-pipeline.mdmarkdown6.9 KB
resources/design-pipeline.mdmarkdown3.2 KB
resources/desktop-pipeline.mdmarkdown3.5 KB
resources/discovery-protocol.mdmarkdown3.3 KB
resources/e2e-pipeline.mdmarkdown7.7 KB
resources/explain-pipeline.mdmarkdown972 B
resources/fix-pipeline.mdmarkdown5.6 KB
resources/framework-patterns.mdmarkdown8.3 KB
resources/gap-check.mdmarkdown3.4 KB
resources/install-guide.mdmarkdown3.4 KB
resources/instinct-system.mdmarkdown6.8 KB
resources/iterate-pipeline.mdmarkdown2.5 KB
resources/language-reviewers.mdmarkdown18.5 KB
resources/loop-pipeline.mdmarkdown3.5 KB
resources/mcp-configs.mdmarkdown4.7 KB
resources/migrate-pipeline.mdmarkdown1.5 KB
resources/mobile-pipeline.mdmarkdown3.5 KB
resources/mode-reference.mdmarkdown6.1 KB
resources/model-routing.mdmarkdown9.1 KB
resources/orchestration-patterns.mdmarkdown5.9 KB
resources/payment-lemonsqueezy.mdmarkdown5.6 KB
resources/payment-pipeline.mdmarkdown10.6 KB
resources/payment-polar.mdmarkdown3.6 KB
resources/payment-steppay.mdmarkdown4.8 KB
resources/payment-stripe.mdmarkdown6.7 KB
resources/payment-toss.mdmarkdown7.2 KB
resources/pipeline-guide.mdmarkdown6.1 KB
resources/plan-pipeline.mdmarkdown2.4 KB
resources/pm-pipeline.mdmarkdown4.5 KB
resources/qa-pipeline.mdmarkdown8.8 KB
resources/report-pipeline.mdmarkdown3.0 KB
resources/review-pipeline.mdmarkdown8.0 KB
resources/rollback-pipeline.mdmarkdown1.3 KB
resources/security-rules.mdmarkdown17.5 KB
resources/snippets-guide.mdmarkdown4.6 KB
resources/status-dashboard.mdmarkdown5.3 KB
resources/style-guide.mdmarkdown2.7 KB
resources/systematic-debugging.mdmarkdown5.7 KB
resources/tdd-pipeline.mdmarkdown4.4 KB

resources/autopus-spec-system.md

View on GitHub
# Autopus SPEC System — EARS Format

> Absorbed from Autopus-ADK. Use with `/aura spec:` mode.
> SPEC = structured requirements with acceptance criteria, enabling test-first development.

---

## SPEC ID Format

```
SPEC-{3-digit-number}-{slug}
Example: SPEC-001-user-auth, SPEC-042-payment-webhook
```

---

## Directory Structure

```
.autopus/specs/SPEC-{ID}/
├── spec.md         # Requirements (EARS format)
├── acceptance.md   # Acceptance criteria (Given/When/Then)
├── plan.md         # Implementation plan (generated by planner)
└── research.md     # Context fetched (Context7 / web research)
```

---

## spec.md — EARS Format

EARS = Easy Approach to Requirements Syntax. 5 sentence patterns:

```
UBIQUITOUS:   The [system] shall [action].
EVENT-DRIVEN: WHEN [trigger], the [system] shall [action].
UNWANTED:     IF [condition], the [system] shall [action].
OPTIONAL:     WHERE [feature included], the [system] shall [action].
COMPLEX:      WHILE [state], WHEN [trigger], the [system] shall [action].
```

### Template

```markdown
# SPEC-{ID}: {Title}

## Status
- [ ] Draft | [ ] Review | [ ] Approved | [ ] Implemented | [ ] Done

## Summary
One-paragraph description of what this spec covers.

## Scope
- In: [list of included features/behaviors]
- Out: [explicit exclusions]

## Requirements

### Functional
- FR-01: WHEN [trigger], the system shall [action].
- FR-02: The system shall [behavior].
- FR-03: IF [condition], the system shall [fallback].

### Non-Functional
- NFR-01: The system shall respond within [N]ms for [operation].
- NFR-02: The system shall support [N] concurrent [entities].

## Dependencies
- SPEC-XXX: [dependency name]
- External: [library/API]

## Open Questions
- [ ] [Question to resolve before implementation]
```

---

## acceptance.md — Given/When/Then

```markdown
# Acceptance Criteria: SPEC-{ID}

## AC-01: {Scenario Title}
**Given** [initial context / preconditions]
**When** [action taken / event occurs]
**Then** [expected outcome / observable behavior]
**And** [additional assertion]

## AC-02: {Error Scenario}
**Given** [error condition]
**When** [action taken]
**Then** [error handling behavior]

## AC-03: {Edge Case}
**Given** [boundary condition]
**When** [trigger]
**Then** [expected behavior at boundary]
```

### Acceptance Coverage Rule

The validator (Gate 2/3) MUST verify each AC maps to at least one:
- Test function (unit/integration)
- OR implementation behavior

Unmapped ACs = Gate FAIL.

---

## plan.md — Implementation Plan

Auto-generated by planner agent. Contains:

```markdown
# Implementation Plan: SPEC-{ID}

## Complexity: HIGH | MEDIUM | LOW
## Estimated Files: N

## File Manifest
| File | Action | Agent Profile | Lines (est.) |
|------|--------|--------------|--------------|
| src/auth/login.ts | CREATE | typescript | 80 |
| src/auth/login.test.ts | CREATE | typescript | 60 |

## Implementation Order
1. [File with no dependencies]
2. [File that depends on #1]
...

## Notes
- [Any constraint or architectural decision]
```

---

## research.md — Context & Docs

Auto-populated during Phase 1.8 (Context7 doc fetch).

```markdown
# Research: SPEC-{ID}

## Libraries Used
- [library-name] v[version]

## Key API Docs
[fetched documentation snippets]

## Prior Art / References
- [relevant existing code in project]
- [external references]

## Architectural Decisions
- [Decision made during planning]
```

---

## `/aura spec:` Mode

```bash
/aura spec:new [title]        → Create new SPEC with next available ID
/aura spec:list               → Show all SPECs and their status
/aura spec:show SPEC-001      → Display spec + acceptance criteria
/aura spec:implement SPEC-001 → Run full pipeline for this SPEC
/aura spec:validate SPEC-001  → Run acceptance coverage check
/aura spec:done SPEC-001      → Mark as implemented + archive
```

### Pipeline Integration

When user runs `/aura spec:implement SPEC-001`:
1. Load `spec.md` + `acceptance.md` → context for all agents
2. Phase 1.5: tester reads acceptance.md → writes failing tests (Given/When/Then → test functions)
3. Phase 2: executor reads spec.md + acceptance.md FIRST (Step 0) before writing any code
4. Gate 2: validator checks acceptance coverage (all ACs mapped)
5. Report match rate: `{implemented ACs} / {total ACs} × 100%`

---

## SPEC Lifecycle

```
Draft → Review → Approved → [Phase 1 Planning] → [Phase 1.5 Tests] →
[Phase 2 Implementation] → [Gate 2: ACs ≥ 90%] → [Phase 4 Review] → Done
```

Status tracked in `spec.md` header checkboxes.

---

## Integration with Lore Commit

Each commit implementing a SPEC should reference it:
```
feat(auth): implement JWT login flow

Directive: Implements SPEC-001 AC-01, AC-02, AC-03
Tested: auth/login.test.ts — 3 scenarios from acceptance.md
```

See `autopus-lore-commit.md` for full trailer protocol.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall