smorky850612/Aurakit / skills/aura
aura
VerifiedAll-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.
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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |