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.
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.
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.
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 β
ββββββββββββ ββββββββββ ββββββββ βββββββββββ
| 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
- Update
lmfso it remains learning-first but also includes copyable code blocks when implementation detail is needed. - Position
/lmfas the manual-coding alternative to/executewhen the user wants to type the code themselves instead of having the agent apply it automatically.
- Add
write-prdskill. Add/prdcommand for Claude Code and Antigravity.
- Add
lmfskills. Add/lmfcommand for Claude Code and Antigravity.
- π§ ALENA identity and public release reset β the toolkit starts at
v1.0.0with 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.cjsplus 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.jsentrypoint, scoped GitHub Packages support, and documentation aligned to the1.0.0ALENA release line.
npx @radenadri/skills-alena addThis 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.
npx @radenadri/skills-alena add --agent claude-code
npx @radenadri/skills-alena add --agent cursor
npx @radenadri/skills-alena add --agent antigravitynpx @radenadri/skills-alena add persistent-memory agent-team-coordination
npx @radenadri/skills-alena add code-review systematic-debuggingnpx @radenadri/skills-alena listAfter installing skills, your workflow depends on whether you're starting fresh or joining an existing codebase.
If you only have an idea, a product problem, or a rough feature request, start with /prd before engineering planning.
/prdclarifies the user, problem, goals, non-goals, constraints, and success metrics./discusslocks implementation preferences and trade-off decisions before planning./planturns 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
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 decisionsYou'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| π’ 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 |
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 |
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:
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.
| # | 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 |
| # | 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 |
| # | 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 |
| # | 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. |
| # | 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 |
| # | 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 |
| # | 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 are Claude Code slash commands (.md files installed to .claude/commands/). They provide structured workflows for common project tasks.
| 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 |
| 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 |
| 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 |
| 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 |
| Command | Description |
|---|---|
/quick |
β‘ Execute small, well-defined tasks without full project planning |
/commit |
π¦ Create well-formatted Conventional Commits with proper scope and body |
| Command | Description |
|---|---|
/memory |
πΎ Persistent memory management β init, read, write, compress, status operations |
/team |
π€ Multi-role team coordination β start, resume, next, board, status operations |
| 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 |
| 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 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 |
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 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 |
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 |
Every AI session starts from scratch. You explain the same architecture, repeat the same decisions, and lose context.
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
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 dashboardSESSION 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 β
ββββββββββββββββββββββ ββββββββββββββββββββββββββ ββββββββββββββββββββββ
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.mdInstall the memory-protocol.mdc rule (auto-installed with npx @radenadri/skills-alena add).
Use /memory init to initialize, /memory write to save.
| 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 |
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!
# 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| 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 |
| 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.
| 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/ |
β |
| 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 |
| 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 |
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 listThis 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. |
MIT Β© Adriana Eka Prayudha. Original upstream copyright notice remains in LICENSE.