Skip to content

radenadri/skills-alena

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

15 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

🧠 ALENA (Autonomous Layer for Executing Networked Agents)

A personal toolkit for autonomous, networked AI agents β€” 35 skills Β· 36 commands Β· 39 workflows Β· 9 agents Β· 10 cursor rules Β· 8 hooks Β· 13 modules Β· 11 templates

Make your AI coding assistant operate like your own disciplined toolkit.

Get Started NPM Version License Stars

GitHub Wiki


🌟 What is This?

ALENA is a personal toolkit for autonomous, networked AI agents. The long form is Autonomous Layer for Executing Networked Agents. Install once, use everywhere β€” across 34+ supported agents including Antigravity, Cursor, Claude Code, Gemini CLI, Windsurf, Copilot, and more.


πŸ’Ž LLM Council v2 β€” Agent Team Coordination

The Problem

AI coding tasks fail at scale because no single agent can hold all context: database schemas, API routes, service dependencies, frontend components, and business logic β€” simultaneously. Linear handoffs lose context. Role-switching in a single context window wastes tokens.

The Solution: Real Subagent Spawning + Deterministic Orchestration

Council v2 replaces the old role-switching pattern with real subagent spawning via Task(). Each specialist agent gets a fresh 200k context window β€” no shared context pollution. The orchestrator stays lean at ~10-15% context usage.

                    ╔═══════════════════════════════╗
                    β•‘     🎯 ORCHESTRATOR (lean)      β•‘
                    β•‘  ~10-15% context usage           β•‘
                    β•‘  13 deterministic CLI commands    β•‘
                    β•‘  Code-enforced quality gates      β•‘
                    β•šβ•β•β•β•β•β•β•β•β•β•β•β•β•¦β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•
                                 β•‘
                        Task() spawning
              β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
       β”Œβ”€β”€β”€β”€β”€β”€β–Όβ”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β–Όβ”€β”€β” β”Œβ”€β”€β–Όβ”€β”€β”€β”€β” β”Œβ”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”
       β”‚πŸ”¬Researchβ”‚ β”‚πŸ“Plannerβ”‚ β”‚βš™οΈExec β”‚ β”‚πŸ”Review β”‚
       β”‚ Fresh    β”‚ β”‚ Fresh   β”‚ β”‚ Fresh β”‚ β”‚ Fresh   β”‚
       β”‚ 200k ctx β”‚ β”‚ 200k   β”‚ β”‚ 200k  β”‚ β”‚ 200k   β”‚
       β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Key Capabilities

Capability Description
🧠 Real subagent spawning Each agent gets a fresh 200k context via Task() β€” no shared context pollution
πŸŽ›οΈ 13 CLI commands Deterministic state machine for council orchestration (council start, council next, council status, etc.)
πŸšͺ Code-enforced quality gates Agents cannot advance phases without passing automated gate checks
🎯 6 presets Full, Rapid, Debug, Architecture, Refactoring, Audit councils
πŸ“ Lean orchestrator Orchestrator uses ~10-15% context β€” delegates deep work to specialists
🧠 Memory Module Deep intelligence layer: schemas, routes, services, components, tech stack

What makes it different:

  • βœ… Real subagent spawning β€” each agent gets a fresh 200k context via Task(), no context pollution
  • βœ… 13 deterministic CLI commands β€” council start, council next, council status, etc.
  • βœ… Code-enforced quality gates β€” agents cannot advance phases without passing automated checks
  • βœ… 6 presets β€” Full, Rapid, Debug, Architecture, Refactoring, Audit
  • βœ… Lean orchestrator β€” stays at ~10-15% context, delegates deep work to specialists
  • βœ… Zero infrastructure β€” pure file-based, works in ANY agent environment

πŸ”„ Version History

1.2.1 β€” Improve /lmf for manual coding

  • Update lmf so it remains learning-first but also includes copyable code blocks when implementation detail is needed.
  • Position /lmf as the manual-coding alternative to /execute when the user wants to type the code themselves instead of having the agent apply it automatically.

1.2.0 β€” Add /prd command

  • Add write-prd skill. Add /prd command for Claude Code and Antigravity.

1.1.0 β€” Add /lmf command

  • Add lmf skills. Add /lmf command for Claude Code and Antigravity.

1.0.0 β€” Initial ALENA Release

  • 🧠 ALENA identity and public release reset β€” the toolkit starts at v1.0.0 with ALENA branding, updated install commands, refreshed docs, and release surfaces aligned under the new package and repository.
  • πŸ€– Full asset library included β€” ships with 35 skills, 36 commands, 39 workflows, and 9 specialist agents covering brainstorming, planning, PRD creation, execution, debugging, auditing, review, verification, memory, and team coordination.
  • βš™οΈ Deterministic planning core β€” planning-tools.cjs plus 12 supporting CLI modules handle state, phase, roadmap, verification, frontmatter, config, templates, milestones, model resolution, and council coordination without relying on brittle freeform markdown edits.
  • πŸ›οΈ Council system built in β€” real subagent spawning, structured handoffs, code-enforced quality gates, task boards, and 6 presets (full, rapid, debug, architecture, refactoring, audit) are included in the first release.
  • πŸͺ Hook and session tooling β€” includes 8 hooks for statusline, update checks, context monitoring, memory capture, cost tracking, and related session behavior where the target runtime supports them.
  • πŸ“ Templates and rules layer β€” includes 11 templates plus the core ruleset for anti-hallucination behavior, severity reporting, memory discipline, and evidence-based verification.
  • 🌐 Cross-agent portability β€” installation and generated entrypoint content support 34+ AI coding agents, with native directory/layout handling across Claude Code, Cursor, Windsurf, Gemini/Antigravity, Copilot, Codex, and more.
  • πŸ’Ύ File-based memory and planning state β€” .planning/ artifacts, manifests, and markdown state keep the toolkit portable, inspectable, and repository-friendly without requiring external infrastructure.
  • πŸ§ͺ Publishable CLI package β€” the release includes the npm package identity, built dist/cli.js entrypoint, scoped GitHub Packages support, and documentation aligned to the 1.0.0 ALENA release line.

πŸš€ Quick Start

Install globally (recommended)

npx @radenadri/skills-alena add

This auto-detects your installed agents and installs everything β€” skills, commands, workflows, agents, and rules β€” to the right directories.

In 1.0.0, hooks such as security-gate, statusline, and context-monitor are registered automatically during installation. Run /team to start a multi-agent council session.

Install to a specific agent

npx @radenadri/skills-alena add --agent claude-code
npx @radenadri/skills-alena add --agent cursor
npx @radenadri/skills-alena add --agent antigravity

Install specific skills only

npx @radenadri/skills-alena add persistent-memory agent-team-coordination
npx @radenadri/skills-alena add code-review systematic-debugging

See everything available

npx @radenadri/skills-alena list

🏁 Getting Started β€” Greenfield vs Brownfield

After installing skills, your workflow depends on whether you're starting fresh or joining an existing codebase.

First question: do you need a PRD?

If you only have an idea, a product problem, or a rough feature request, start with /prd before engineering planning.

  • /prd clarifies the user, problem, goals, non-goals, constraints, and success metrics.
  • /discuss locks implementation preferences and trade-off decisions before planning.
  • /plan turns the approved PRD or clarified request into implementation work.

Think of it as:

/prd = what and why
/discuss = preference and trade-off lock-in
/plan = how to build it

🟒 New Project (Greenfield)

You're building something from scratch. No existing code, no legacy decisions.

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚  GREENFIELD WORKFLOW                                            β”‚
β”‚                                                                 β”‚
β”‚  Step 0 ─ /prd (optional)                                       β”‚
β”‚           Use when the project or feature idea is still fuzzy    β”‚
β”‚           Produces a product requirements document first         β”‚
β”‚                          β–Ό                                      β”‚
β”‚  Step 1 ─ /init-project                                         β”‚
β”‚           Creates .planning/ structure, ROADMAP, REQUIREMENTS    β”‚
β”‚           Bootstraps memory system + config.json                 β”‚
β”‚           (Uses: node planning-tools.cjs init)                   β”‚
β”‚                          β–Ό                                      β”‚
β”‚  Step 2 ─ /discuss                                              β”‚
β”‚           Multiple-choice questions with recommendations         β”‚
β”‚           Quick-answer: "1A 2B 3C 4A 5A"                        β”‚
β”‚           Locks decisions in CONTEXT.md                          β”‚
β”‚                          β–Ό                                      β”‚
β”‚  Step 3 ─ /plan                                                 β”‚
β”‚           Creates 2-3 task plan respecting locked decisions      β”‚
β”‚           Each task has <files> <action> <verify> <done>         β”‚
β”‚                          β–Ό                                      β”‚
β”‚  Step 4 ─ /execute                                              β”‚
β”‚           Task-by-task execution with checkpoints                β”‚
β”‚           Deviation protocol for plan changes                    β”‚
β”‚           State tracked by planning-tools.cjs                    β”‚
β”‚                          β–Ό                                      β”‚
β”‚  Step 5 ─ /verify                                               β”‚
β”‚           Validates implementation against the plan              β”‚
β”‚           Gap closure if anything was missed                     β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Quick start for greenfield:

# 1. Install skills
npx @radenadri/skills-alena add

# 2. If the product idea is still fuzzy, start here:
/prd "describe the product or feature idea"

# 3. Then tell your AI agent:
/init-project

# 4. The agent will walk you through:
#    β†’ Project context gathering
#    β†’ Requirements capture
#    β†’ Roadmap phases
#    β†’ Then suggest /discuss to lock decisions

🟑 Existing Codebase (Brownfield)

You're joining a project that already has code, patterns, and decisions. The AI needs to learn the codebase BEFORE making changes.

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚  BROWNFIELD WORKFLOW                                            β”‚
β”‚                                                                 β”‚
β”‚  Step 1 ─ /memory init                                          β”‚
β”‚           Creates .planning/ structure for the existing project  β”‚
β”‚           (Uses: node planning-tools.cjs init)                   β”‚
β”‚                          β–Ό                                      β”‚
β”‚  Step 2 ─ Codebase Mapping (automatic)                          β”‚
β”‚           Agent scans: file structure, patterns, tech stack      β”‚
β”‚           Writes: MEMORY.md with project brain                   β”‚
β”‚           Captures: architecture, conventions, known issues      β”‚
β”‚                          β–Ό                                      β”‚
β”‚  Step 3 ─ /prd (optional)                                       β”‚
β”‚           Use for new feature work that needs product clarity    β”‚
β”‚           Grounds the PRD in the real codebase constraints       β”‚
β”‚                          β–Ό                                      β”‚
β”‚  Step 4 ─ /discuss                                              β”‚
β”‚           "I want to add [feature] to this existing project"     β”‚
β”‚           Agent asks MCQ questions considering existing patterns  β”‚
β”‚           Quick-answer: "1A 2B 3C 4A"                           β”‚
β”‚                          β–Ό                                      β”‚
β”‚  Step 5 ─ /plan                                                 β”‚
β”‚           Creates plan that respects existing architecture       β”‚
β”‚           References real files, real patterns, real conventions  β”‚
β”‚                          β–Ό                                      β”‚
β”‚  Step 6 ─ /execute                                              β”‚
β”‚           Implements following existing patterns                 β”‚
β”‚           codebase-conformity skill ensures consistency           β”‚
β”‚                          β–Ό                                      β”‚
β”‚  Step 7 ─ /verify                                               β”‚
β”‚           Validates against plan + existing test suite            β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Quick start for brownfield:

# 1. Install skills into your existing project
npx @radenadri/skills-alena add

# 2. Tell your AI agent:
/memory init

# 3. Let the agent scan your codebase

# 4. If the feature needs product clarification, do this next:
/prd "describe the feature or product problem"

# 5. Then lock implementation decisions:
/discuss add user preferences feature

# 6. Answer the MCQ questions, then:
/plan
/execute

Key Differences

🟒 Greenfield 🟑 Brownfield
First step /init-project (full setup) /memory init (lightweight)
Context source Your answers to questions Codebase scanning β†’ MEMORY.md
Patterns You define them Agent discovers existing patterns
Planning Free to choose any approach Must respect existing architecture
Risk Low (no breaking changes) Higher (must be compatible)
Skills activated writing-plans, executing-plans + codebase-mapping, codebase-conformity

The /discuss Quick-Answer Format

When the agent presents multiple-choice questions, you can answer everything in one line:

### ⚑ Quick Answer

> All recommended: 1A 2B 3A 4B 5A
>
> Your answer: 1A 2B 3C 4A 5:"use Redis for sessions"
Format Meaning
1A Question 1, Option A
2B Question 2, Option B
5:"custom text" Question 5, Custom answer
Just press Enter Accept all recommendations

πŸ—οΈ Supported Agents

ALENA works with 30+ AI coding agents. 12 platforms have full asset parity (Claude Code, Copilot, Codex, Cursor, Windsurf, Cline, Roo, Amp, Augment, Continue, Kilo, Goose). Each agent gets assets installed to its native directory:

Agent Skills Commands Workflows Rules
Claude Code .claude/skills/ .claude/commands/ β€” β€”
Cursor .cursor/skills/ β€” β€” .cursor/rules/
Antigravity (Gemini) .agent/skills/ β€” .agent/workflows/ β€”
Gemini CLI .gemini/skills/ β€” β€” β€”
GitHub Copilot .github/skills/ β€” β€” β€”
Windsurf .windsurf/skills/ β€” β€” β€”
Cline .cline/skills/ β€” β€” β€”
Roo .roo/skills/ β€” β€” β€”
Codex .agents/skills/ β€” β€” β€”
Amp .agents/skills/ β€” β€” β€”
Kilo Code .kilocode/skills/ β€” β€” β€”
Augment .augment/skills/ β€” β€” β€”
Continue .continue/skills/ β€” β€” β€”
Goose .goose/skills/ β€” β€” β€”
OpenCode .agents/skills/ β€” β€” β€”
Trae .trae/skills/ β€” β€” β€”
Junie .junie/skills/ β€” β€” β€”
OpenClaw skills/ β€” β€” β€”
OpenHands .openhands/skills/ β€” β€” β€”
Kode .kode/skills/ β€” β€” β€”
Qoder .qoder/skills/ β€” β€” β€”
Mux .mux/skills/ β€” β€” β€”
Zencoder .zencoder/skills/ β€” β€” β€”
Crush .crush/skills/ β€” β€” β€”
Droid .factory/skills/ β€” β€” β€”
Command Code .commandcode/skills/ β€” β€” β€”
CodeBuddy .codebuddy/skills/ β€” β€” β€”
Mistral Vibe .vibe/skills/ β€” β€” β€”
Qwen Code .qwen/skills/ β€” β€” β€”
Pi .pi/skills/ β€” β€” β€”
Replit .agents/skills/ β€” β€” β€”
Kiro CLI .kiro/skills/ β€” β€” β€”
iFlow CLI .iflow/skills/ β€” β€” β€”
Kimi CLI .agents/skills/ β€” β€” β€”

πŸ“š Complete Asset Catalog

🧠 Skills (35)

Skills are deep instructional documents that teach AI agents HOW to think about specific engineering tasks. Each skill contains principles, protocols, anti-patterns, and quality criteria.

πŸ”· Core Development (10 skills)

# Skill Description
1 πŸ’‘ brainstorming Creative ideation β€” mind maps, structured exploration, and divergent thinking before any feature work
2 πŸ“„ write-prd Product requirements writing β€” interview-first wrapper skill that turns feature ideas into structured PRDs before engineering planning β€” ✨ NEW
3 🧭 lmf Learning-first mode flow β€” wrapper skill that combines brainstorming, writing-plans, and writing-documentation into a tutorial-first orchestration pattern with copyable code when manual implementation is needed β€” ✨ NEW
4 πŸ“ writing-plans Task decomposition β€” dependency-aware plans with effort estimates, risk assessments, and implementation waves
5 βš™οΈ executing-plans Plan execution β€” wave-based implementation with checkpoints, inline verification, and state tracking
6 πŸ§ͺ test-driven-development TDD methodology β€” red-green-refactor cycle, test architecture, fixture patterns, and coverage strategies
7 πŸ› systematic-debugging Scientific debugging β€” hypothesis-driven investigation with evidence chains and root cause analysis
8 πŸ” code-review Structured code review β€” security, performance, correctness checks with severity-based feedback
9 βœ… verification-before-completion Completion gates β€” automated checks, compliance verification, and regression testing before marking done
10 πŸ“¦ git-workflow Git best practices β€” conventional commits, branching strategies, PR workflows, and conflict resolution

πŸ”Ά Auditing (10 skills)

# Skill Description
11 πŸ›οΈ architecture-audit Architecture review β€” modularity, coupling, SOLID compliance, dependency direction, and scalability assessment
12 πŸ”’ security-audit Security assessment β€” OWASP top 10, auth flows, input validation, secrets management, and vulnerability scanning
13 ⚑ performance-audit Performance profiling β€” N+1 queries, bundle sizes, runtime bottlenecks, caching opportunities, and load testing
14 πŸ—„οΈ database-audit Database health β€” schema design, indexing strategy, query optimization, migrations, and normalization review
15 🎨 frontend-audit Frontend quality β€” component architecture, state management, rendering efficiency, and responsive design
16 🌐 api-design-audit API design review β€” REST/GraphQL conventions, versioning, error handling, pagination, and documentation
17 πŸ“¦ dependency-audit Dependency health β€” outdated packages, security vulnerabilities, license compliance, and bundle impact
18 πŸ“Š observability-audit Observability review β€” logging strategy, metrics, tracing, alerting, and production debugging capability
19 β™Ώ accessibility-audit Accessibility compliance β€” WCAG standards, keyboard navigation, screen reader support, and color contrast
20 πŸ”„ ci-cd-audit CI/CD pipeline review β€” build times, test reliability, deployment safety, and pipeline optimization

πŸ”· Evolution (4 skills)

# Skill Description
21 ♻️ refactoring-safely Safe refactoring β€” incremental transformation with test coverage, feature flags, and rollback strategies
22 πŸ“– writing-documentation Documentation authoring β€” API docs, architecture diagrams, README standards, and knowledge transfer
23 πŸ—ΊοΈ codebase-mapping Codebase analysis β€” module boundaries, dependency graphs, entry points, and health metrics
24 🚨 incident-response Incident handling β€” triage protocols, root cause analysis, post-mortems, and prevention measures

🟣 Agent Intelligence (2 skills)

# Skill Description
25 πŸ’Ύ persistent-memory Automated session memory β€” captures decisions, context, and learnings across sessions via file-based protocols. Zero infrastructure, works in ANY agent. Inspired by claude-mem.
26 πŸ’Ž agent-team-coordination LLM Council β€” Manager-orchestrated multi-agent coordination with Memory Module. Manager has full project knowledge (schemas, routes, services), dynamically routes tasks to specialist sub-agents, enables peer communication, handles escalations across 6 council presets.

πŸ”Ά Integration & Completeness (4 skills)

# Skill Description
27 πŸ”— full-stack-api-integration End-to-end API integration β€” spec analysis, surface mapping, SOLID-compliant API layer design, systematic endpoint implementation, and integration testing
28 πŸ₯ product-completeness-audit Functional completeness verification β€” 5-level completeness spectrum, placeholder detection, broken flow identification, and API connection validation
29 πŸ”¬ brutal-exhaustive-audit No-shortcuts 5-pass audit β€” build verification, route checking, data flow tracing, user flow testing, and edge case validation with anti-shortcut rules
30 πŸ”„ codebase-conformity Pattern uniformity enforcement β€” read existing patterns before writing, match them exactly, and double-verify conformity before claiming done

πŸ”€ Migration (1 skill)

# Skill Description
31 πŸ”€ nextjs-to-nuxt-migration Next.js β†’ Nuxt 4 migration β€” submodule analysis, backend verification, multi-pass execution (backend wiring β†’ feature completeness β†’ CSS polish β†’ verification), sidebar registration, theme/dark-mode rules, URL encoding, Agent Team File Protocol, and Playwright visual QA

πŸ”Έ Meta (5 skills)

# Skill Description
32 πŸ“˜ using-skills How to use and combine skills effectively in your workflow
33 ✍️ writing-skills How to create new skills β€” format, quality standards, and testing requirements
34 🎨 ui-ux-redesign Full-stack visual audit β€” inventories backend APIs, audits every component and design token, analyzes user flows, and produces layered redesign recommendations
35 πŸ“ _rules Master rules skill β€” consolidates core principles, anti-hallucination protocol, severity framework, and skill activation table

⚑ Commands (36)

Commands are Claude Code slash commands (.md files installed to .claude/commands/). They provide structured workflows for common project tasks.

πŸ”· Project Lifecycle

Command Description
/init-project πŸ—οΈ Initialize a new project with .planning/ directory β€” PROJECT.md, REQUIREMENTS.md, ROADMAP.md, STATE.md, config.json. Uses planning-tools.cjs for deterministic bootstrapping.
/discuss πŸ’¬ Pre-planning MCQ decision capture β€” presents multiple-choice questions with recommendations, quick-answer format (1A 2B 3C), locks decisions in CONTEXT.md
/prd πŸ“„ Product requirements drafting β€” interview-first flow that uses the local write-prd wrapper skill to produce a reusable PRD before implementation planning β€” ✨ NEW
/lmf 🧭 Learning-first tutorial flow β€” uses the local lmf wrapper skill to combine explanation, planning, and copyable code guidance before execution β€” ✨ NEW
/plan πŸ“‹ Create a 2-3 task implementation plan with task anatomy (<files> <action> <verify> <done>), context budgets, and locked decision enforcement
/execute βš™οΈ Execute an implementation plan with deviation protocol (4 categories), checkpoint system, and planning-tools.cjs state management
/verify βœ… Validate implementations against plans β€” automated checks, compliance verification, regression testing, conversational UAT
/progress πŸ“Š Display project progress, phase status, and task completion from .planning/ state files
/settings βš™οΈ View/modify project config β€” mode (interactive/auto), depth (quick/standard/comprehensive), workflow preferences

πŸ”· Research & Documentation

Command Description
/research πŸ”¬ Deep research on topics before planning β€” generates structured reports in .planning/research/
/doc πŸ“– Generate documentation for code, APIs, architecture, or setup
/explain πŸ’‘ Provide detailed explanations of code, architecture, or concepts

πŸ”· Code Quality

Command Description
/review πŸ” Structured code review with severity-based feedback (critical/major/minor/nit)
/test πŸ§ͺ Generate and run tests β€” unit, integration, e2e with coverage reporting
/debug πŸ› Scientific debugging with hypothesis tracking and evidence chains
/fix-issue πŸ”§ Diagnose and fix specific issues with minimal changes and regression testing
/refactor ♻️ Safe refactoring with test coverage and incremental transformation

πŸ”· Operations & Security

Command Description
/migrate πŸ—„οΈ Database or code migrations with safety checks, rollback strategies, and data validation
/performance ⚑ Profile and analyze application performance with benchmarking
/security-scan πŸ”’ Comprehensive security scan β€” OWASP top 10, secrets detection, dependency vulnerabilities
/deploy-check πŸš€ Pre-deployment validation checklist
/audit πŸ“‹ Full codebase audit β€” linting, secrets, console logs, TODOs

πŸ”· Workflow

Command Description
/quick ⚑ Execute small, well-defined tasks without full project planning
/commit πŸ“¦ Create well-formatted Conventional Commits with proper scope and body

🟣 Agent Intelligence

Command Description
/memory πŸ’Ύ Persistent memory management β€” init, read, write, compress, status operations
/team 🀝 Multi-role team coordination β€” start, resume, next, board, status operations

πŸ”Ά Integration & Auditing

Command Description
/integrate πŸ”— Full-stack API integration from spec β€” surface mapping, SOLID architecture, endpoint implementation, and verification
/health-check πŸ₯ Product completeness audit β€” route inventory, placeholder detection, flow testing, and API connection checks
/deep-audit πŸ”¬ Brutal exhaustive 5-pass audit β€” build, routes, data flow, user flows, and edge cases with anti-shortcut rules
/redesign 🎨 Full UI/UX redesign audit β€” visual audit, component census, token extraction, UX analysis, layered redesign plan

🟑 Intelligence & Orchestration

Command Description
/learn πŸ“š Extract reusable patterns from sessions across 8 categories with deduplication, persisted to .planning/LEARNINGS.md
/quality-gate βœ… 6-step quality pipeline (Build β†’ Type Check β†’ Lint β†’ Test β†’ Security β†’ Diff) with 4 modes: quick, full, pre-commit, pre-pr
/checkpoint πŸ“ Named progress snapshots with create/verify/list modes stored in .planning/checkpoints/
/loop πŸ” Bounded loop execution β€” repetitive tasks with safety bounds (max iterations, stall detection, test-between-iterations)
/orchestrate πŸ”— Multi-agent orchestration β€” chain agents in predefined sequences (feature, bugfix, refactor, security) with structured handoffs
/context 🎯 Context mode switching β€” dev (code-first), research (read-widely), review (quality-first) modes that change workflow behavior

πŸ”„ Workflows (39)

Workflows are Antigravity step-by-step execution scripts (.md files installed to .agent/workflows/). Many include // turbo annotations for auto-execution.

Workflow Description
/init-project πŸ—οΈ Initialize project with .planning/ structure
/discuss πŸ’¬ Pre-planning MCQ discussion with quick-answer
/prd πŸ“„ Product requirements workflow that mirrors the local write-prd wrapper skill in Antigravity β€” ✨ NEW
/lmf 🧭 Learning-first tutorial workflow that mirrors the local lmf wrapper skill in Antigravity, including copyable code when implementation is needed β€” ✨ NEW
/plan-feature πŸ“‹ Plan a feature with research, design, and task decomposition
/execute βš™οΈ Execute plans with wave-based steps and verification
/verify βœ… Validate implementation against plans
/research πŸ”¬ Deep research with structured report output
/progress πŸ“Š Display project status and completion
/quick ⚑ Quick task execution without full planning
/debug πŸ› Scientific debugging workflow
/fix-issue πŸ”§ Issue diagnosis and fix
/review πŸ” Structured code review
/test πŸ§ͺ Test generation and execution
/refactor ♻️ Safe refactoring with tests
/commit πŸ“¦ Conventional commit creation
/doc πŸ“– Documentation generation
/explain πŸ’‘ Code explanation
/audit πŸ“‹ Codebase audit
/security-scan πŸ”’ Security scanning
/performance ⚑ Performance profiling
/migrate πŸ—„οΈ Database/code migration
/deploy-check πŸš€ Deployment validation
/release 🏷️ Release preparation
/codebase-map πŸ—ΊοΈ Codebase analysis and mapping
/deps-update πŸ“¦ Dependency updates
/incident-response 🚨 Incident triage and response
/memory-sync πŸ’Ύ Memory read/write/compress operations
/team-session 🀝 Multi-role team coordination
/integrate-api πŸ”— Full-stack API integration workflow
/product-health-check πŸ₯ Product completeness audit workflow
/deep-audit πŸ”¬ Brutal exhaustive audit workflow
/redesign 🎨 Full UI/UX redesign workflow
/gap-closure πŸ”§ Close execution gaps with focused mini-plans

πŸ€– Agents (9)

Agent definitions are specialist AI personas (.md files installed to .claude/agents/). Each agent has detailed protocols, principles, and anti-patterns.

Agent Emoji Description
researcher πŸ”¬ Deep codebase and domain research β€” gathers comprehensive evidence and context before planning. Emphasizes accuracy, exhaustive search, and source attribution.
planner πŸ“‹ Plans-as-prompts β€” generates dependency-aware plans with task anatomy (<files> <action> <verify> <done>), context budgets, locked decision enforcement, and multi-plan sequencing.
executor βš™οΈ Plan execution with deviation protocol β€” implements tasks with checkpoint handling (standard/context/blocker), DON'T/AVOID instruction enforcement, and planning-tools.cjs state management.
reviewer πŸ” Structured code review β€” examines changes for correctness, security, performance, patterns, and maintainability. Provides severity-based feedback.
debugger πŸ› Scientific debugging with hypothesis tracking β€” investigates issues using hypothesis-driven methodology with evidence chains and persistent state.
verifier βœ… Work verification and gap analysis β€” validates implementation against plans, runs comprehensive checks, identifies gaps, and generates fix plans.
mapper πŸ—ΊοΈ Codebase mapping and dependency analysis β€” analyzes project structure, module boundaries, dependencies, patterns, and health metrics.
investigator πŸ•΅οΈ Deep investigation for Debug Council β€” forensic analysis of complex bugs with evidence chains and timeline reconstruction.
fixer πŸ”§ Targeted fix implementation for Debug Council β€” minimal, surgical fixes with regression prevention and rollback strategies.

🎯 Cursor Rules (10)

Cursor rules are .mdc files installed to .cursor/rules/. They guide Cursor AI's behavior for specific concerns.

Rule Description
πŸ—οΈ core-development Code quality standards β€” SOLID principles, DRY, error handling, testing, and Git commit conventions
🚫 anti-hallucination Anti-fabrication protocol β€” mandates verification of APIs, paths, configs before use. Prevents hallucinated code.
πŸ“‹ planning-workflow Structured planning β€” research β†’ design β†’ decompose β†’ estimate β†’ document workflow
πŸ› debugging-protocol Scientific debugging β€” hypothesis β†’ test β†’ evidence β†’ root cause methodology
πŸ”’ security Security best practices β€” auth, input validation, data handling, secrets management
πŸ—„οΈ database Database rules β€” schema design, indexing, query optimization, migrations
πŸ§ͺ testing Testing standards β€” coverage requirements, fixture patterns, assertion quality
πŸ” code-review Code review checklist β€” automated and manual review criteria
πŸ’Ύ memory-protocol Persistent memory β€” auto-read MEMORY.md on start, auto-write on end
🀝 team-protocol Team coordination β€” sequential role-switching with blackboard

πŸ“ Rules (5)

Universal rules (.md files) that can be appended to GEMINI.md, CLAUDE.md, or any agent's system prompt.

Rule Description
πŸ—οΈ core-principles Foundational engineering principles β€” SOLID, DRY, KISS, YAGNI, and clean architecture
🚫 anti-hallucination Verification-first protocol β€” never fabricate APIs, paths, or configs
βš–οΈ severity-framework Issue severity classification β€” critical/major/minor/nit with response criteria
πŸ’Ύ memory-protocol Persistent memory instructions β€” auto-read and auto-write .planning/MEMORY.md
🀝 team-protocol Team coordination instructions β€” role-switching and blackboard protocol

πŸ’Ύ Persistent Memory + State Management

The Problem

Every AI session starts from scratch. You explain the same architecture, repeat the same decisions, and lose context.

The Solution

File-based memory protocol + deterministic state management β€” no hooks, no databases, no external services. Works in ANY agent.

.planning/
β”œβ”€β”€ MEMORY.md                    # 🧠 Project brain (~300 lines max)
β”œβ”€β”€ STATE.md                     # πŸ“ Current position (phase/plan/task)
β”œβ”€β”€ config.json                  # βš™οΈ Mode, depth, preferences
β”œβ”€β”€ sessions/                    # πŸ“ Session logs
β”œβ”€β”€ decisions/DECISIONS.md       # πŸ“‹ Decision log (append-only)
β”œβ”€β”€ plans/                       # πŸ“‹ Implementation plans
β”œβ”€β”€ research/                    # πŸ”¬ Research + CONTEXT.md from /discuss
β”œβ”€β”€ context/
β”‚   β”œβ”€β”€ architecture.md          # πŸ—οΈ Architecture decisions
β”‚   β”œβ”€β”€ patterns.md              # πŸ”„ Established patterns
β”‚   β”œβ”€β”€ gotchas.md               # ⚠️ Known issues
β”‚   └── tech-debt.md             # πŸ”§ Technical debt
└── handoffs/LATEST.md           # πŸ“€ Last session's handoff

planning-tools.cjs β€” Deterministic State Management

LLMs are unreliable at structured file operations. The planning-tools.cjs CLI handles these deterministically:

# Bootstrap the .planning/ directory
node planning-tools.cjs init

# Track execution progress
node planning-tools.cjs state load              # Where am I?
node planning-tools.cjs state advance-task      # Mark task complete
node planning-tools.cjs state add-decision      # Record a decision
node planning-tools.cjs state add-blocker       # Flag a blocker

# Manage configuration
node planning-tools.cjs config get mode         # interactive or auto?
node planning-tools.cjs config set depth comprehensive

# Validate and report
node planning-tools.cjs verify structure        # Is .planning/ intact?
node planning-tools.cjs progress                # Show dashboard

How Memory Works

SESSION START                    DURING SESSION                  SESSION END
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”           β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”      β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ 1. Read MEMORY.md  β”‚           β”‚ 4. planning-tools.cjs  β”‚      β”‚ 8. Create session  β”‚
β”‚ 2. Read LATEST.md  β”‚           β”‚    tracks state changesβ”‚      β”‚    log              β”‚
β”‚ 3. Read config.jsonβ”‚           β”‚ 5. Decisions β†’ log     β”‚      β”‚ 9. Write handoff   β”‚
β”‚    Full context!   β”‚           β”‚ 6. Blockers β†’ flag     β”‚      β”‚ 10. Update memory  β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜           β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜      β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Setup

For Antigravity

Add to ~/.gemini/GEMINI.md:

## 🧠 Automatic Memory Protocol
ALWAYS at the START: read .planning/MEMORY.md and .planning/handoffs/LATEST.md
ALWAYS at the END: update MEMORY.md, write handoffs/LATEST.md

For Cursor

Install the memory-protocol.mdc rule (auto-installed with npx @radenadri/skills-alena add).

For Claude Code

Use /memory init to initialize, /memory write to save.

Comparison with claude-mem

claude-mem ALENA
Infrastructure SQLite + Chroma + Bun Zero βœ…
Agent support Claude Code only ANY agent βœ…
State management None planning-tools.cjs CLI βœ…
Capture method Lifecycle hooks Instruction-based
Storage Database Markdown files (git!)
Setup Plugin install + config Add 4 lines to GEMINI.md

πŸ“ Project Structure

alena/
β”œβ”€β”€ πŸ“‚ skills/                   # 35 deep instructional skills
β”‚   β”œβ”€β”€ brainstorming/SKILL.md
β”‚   β”œβ”€β”€ writing-plans/SKILL.md          # Plans-as-prompts with task anatomy
β”‚   β”œβ”€β”€ executing-plans/SKILL.md        # Deviation protocol + checkpoints
β”‚   β”œβ”€β”€ persistent-memory/SKILL.md
β”‚   β”œβ”€β”€ agent-team-coordination/SKILL.md
β”‚   └── ... (26 more)
β”œβ”€β”€ πŸ“‚ commands/                 # 36 Claude Code slash commands
β”‚   β”œβ”€β”€ init-project.md
β”‚   β”œβ”€β”€ discuss.md                       ✨ MCQ decision capture
β”‚   β”œβ”€β”€ settings.md                      ✨ Config management
β”‚   β”œβ”€β”€ memory.md
β”‚   β”œβ”€β”€ team.md
β”‚   └── ... (23 more)
β”œβ”€β”€ πŸ“‚ workflows/                # 39 Antigravity workflows
β”‚   β”œβ”€β”€ init-project.md
β”‚   β”œβ”€β”€ discuss.md                       ✨ MCQ discussion workflow
β”‚   β”œβ”€β”€ gap-closure.md                   ✨ Execution gap closure
β”‚   β”œβ”€β”€ memory-sync.md
β”‚   β”œβ”€β”€ team-session.md
β”‚   └── ... (27 more)
β”œβ”€β”€ πŸ“‚ agents/                   # 9 specialist agent definitions
β”‚   β”œβ”€β”€ planner.md                       # Plans-as-prompts, locked decisions
β”‚   β”œβ”€β”€ executor.md                      # Deviation protocol, context awareness
β”‚   β”œβ”€β”€ investigator.md                  # Debug Council forensics
β”‚   β”œβ”€β”€ fixer.md                         # Debug Council surgical fixes
β”‚   └── ... (5 more)
β”œβ”€β”€ πŸ“‚ scripts/                  # Deterministic tooling
β”‚   └── planning-tools.cjs              # State management CLI
β”œβ”€β”€ πŸ“‚ cursor-rules/             # 10 Cursor .mdc rules
β”‚   β”œβ”€β”€ core-development.mdc
β”‚   β”œβ”€β”€ memory-protocol.mdc
β”‚   └── ... (8 more)
β”œβ”€β”€ πŸ“‚ rules/                    # 5 universal agent rules
β”‚   β”œβ”€β”€ core-principles.md               # + Context Engineering principle
β”‚   β”œβ”€β”€ memory-protocol.md              # + planning-tools.cjs integration
β”‚   └── ... (3 more)
β”œβ”€β”€ πŸ“‚ docs/                     # Documentation
β”œβ”€β”€ πŸ“‚ src/                      # CLI source
β”‚   └── cli.ts
β”œβ”€β”€ CLAUDE.md                    # Claude Code integration
β”œβ”€β”€ GEMINI.md                    # Gemini/Antigravity integration
β”œβ”€β”€ package.json
└── README.md                    # You are here!

πŸ› οΈ CLI Reference

Commands

# Install everything (auto-detect agents)
npx @radenadri/skills-alena add

# Install to specific agent
npx @radenadri/skills-alena add --agent antigravity
npx @radenadri/skills-alena add --agent cursor
npx @radenadri/skills-alena add --agent claude-code

# Install globally (available in all projects)
npx @radenadri/skills-alena add --global

# Install specific skills
npx @radenadri/skills-alena add persistent-memory code-review
npx @radenadri/skills-alena add lmf brainstorming writing-plans writing-documentation
npx @radenadri/skills-alena add write-prd brainstorming writing-documentation

# Update all skills to latest version
npx @radenadri/skills-alena update

# Show installation status and version
npx @radenadri/skills-alena status

# List all available assets
npx @radenadri/skills-alena list

# Show supported agents
npx @radenadri/skills-alena agents

# Non-interactive install (CI/CD friendly)
npx @radenadri/skills-alena add --all -y -a '*'

# Show help
npx @radenadri/skills-alena help

Flags

Flag Description
-a, --agent <name> Install to a specific agent (use '*' for all)
-g, --global Install globally (user home) instead of project
--all Install all available skills
-y, --yes Non-interactive mode (auto-accept)
--help Show help text

Install Behavior

Asset Local Install Global Install (-g)
Skills Copied to agent dir. Re-running updates existing. Copied to global agent dir.
Commands Copied to .claude/commands/ ❌ Skipped
Workflows Copied to .agent/workflows/ ❌ Skipped
Agent Defs Copied to .claude/agents/ ❌ Skipped
Cursor Rules Copied to .cursor/rules/ ❌ Skipped
CLAUDE.md Appends activation section (preserves your content). Updates on re-install. ❌ Skipped
GEMINI.md Appends activation section (preserves your content). Updates on re-install. ❌ Skipped
Memory Never installed (created at runtime per-project). ❌ Never installed

If you want the full local experience, install locally so wrapper skills can be paired with their agent-specific surfaces. That applies to both lmf and PRD drafting: global install includes the lmf and write-prd skills, but the Claude Code /lmf and /prd commands plus the Antigravity /lmf and /prd workflows are local-only surfaces.

What Gets Installed Where

Asset Type Claude Code Cursor Antigravity
Skills .claude/skills/ .cursor/skills/ .agent/skills/
Commands .claude/commands/ β€” β€”
Workflows β€” β€” .agent/workflows/
Agent Defs .claude/agents/ β€” β€”
Rules β€” .cursor/rules/ β€”

πŸ“– Documentation

Document Description
🌐 Website Product homepage and primary landing page
πŸ“– Wiki Comprehensive GitHub Wiki with guides and reference
skills/write-prd/SKILL.md Local wrapper skill for interview-first PRD creation
commands/prd.md Claude Code /prd product requirements command
workflows/prd.md Antigravity /prd product requirements workflow
skills/lmf/SKILL.md Local wrapper skill for the lmf orchestrator pattern
commands/lmf.md Claude Code /lmf learning-first command
workflows/lmf.md Antigravity /lmf learning-first workflow
Agent Teams & Memory Comprehensive guide to the team coordination and persistent memory systems
Competitive Analysis Analysis of GSD, Claude Code, Cursor, and Antigravity frameworks
Audit Report Comprehensive quality audit report for the ALENA skill library
Contributing How to contribute to this project
Changelog Version history and release notes

πŸ“Š By the Numbers

Metric Count
🧠 Skills 35
⚑ Commands 36
πŸ”„ Workflows 39
πŸ€– Agents 9
🎯 Cursor Rules 10
πŸ“ Rules 5
πŸͺ Hooks 8
πŸ“¦ CLI Modules 13
πŸ“ Templates 11
πŸ“š References 2
πŸŽ›οΈ Council Commands 13
πŸ€– Supported Agents 34

🀝 Contributing

Contributions are welcome! See CONTRIBUTING.md for guidelines.

# Clone the repo
git clone https://github.com/radenadri/skills-alena.git

# Install dependencies
npm install

# Build
npm run build

# Test locally
node dist/cli.js list

πŸ™ Acknowledgments

This project stands on the shoulders of giants. Huge thanks to these projects that inspired and influenced the design of ALENA:

Project Author Contribution
Skills by Amrit Amritpal Singh Boparai Direct inspiration for ALENA's skills-driven structure, planning workflows, and multi-agent toolkit direction.
Superpowers Jesse Vincent (@obra) Pioneered the agentic skills framework concept β€” composable skills, TDD-first workflows, and subagent-driven development. The foundation we all build on.
GSD (Get Shit Done) @glittercowboy Spec-driven development with context rot prevention, parallel agent spawning, and executable plans. Showed how to keep AI agents focused and productive.
Agent Skills Standard Anthropic The open standard for packaging and sharing AI agent capabilities via SKILL.md files.
skills.sh Community The agent skills directory and CLI that makes skill discovery and installation universal.

πŸ“„ License

MIT Β© Adriana Eka Prayudha. Original upstream copyright notice remains in LICENSE.

About

ALENA is a personal toolkit for autonomous, networked AI agents

Topics

Resources

License

Contributing

Stars

Watchers

Forks

Packages

 
 
 

Contributors