By Avila-Tek
Complete Avila Tek software delivery lifecycle — from Design Doc to production code
Implement the next task incrementally — build, test, verify, commit — implementa esto / construye paso a paso
Simplify code for clarity and maintainability — reduce complexity without changing behavior — simplifica esto / reduce la complejidad
Refactor an existing test suite — snapshot, classify, restructure module by module, compare. — refactoriza las pruebas / arregla los tests
Run TDD workflow — write failing tests, implement, verify. For bugs, use the Prove-It pattern. — escribe las pruebas / crea los tests
Sync epics and stories from the repo to Lark Base via the Avila Tools API — sincroniza el backlog / sube a Lark
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.
QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
Automatically upgrades dependencies of any project that belongs to the JavaScript/Node.js ecosystem and has a package.json. Use when the user asks to upgrade the dependencies of a specific project.
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend. Spanish triggers: "diseña esta API", "define el contrato", "diseño de endpoint REST".
Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data via Chrome DevTools MCP. Spanish triggers: "prueba en el navegador", "inspecciona el DOM", "verifica en el browser".
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies. Spanish triggers: "configura el CI", "configura el pipeline", "automatiza el build".
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch. Spanish triggers: "revisa el código", "revisión de código", "revisa este PR".
Requires secrets
Needs API keys or credentials to function
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Claude Code skills for the complete Avila Tek software delivery lifecycle — from product doc to production code.
TDD in this project = Technical Design Document. Never Test-Driven Development.
Two tracks. One system.
The Planning Track (Tech Lead) transforms a Design Doc into structured story files: context, domain model, functional spec, epics, and user stories — each with acceptance criteria and full technical scope. The Dev Track (Developer) picks up those story files and delivers production code using 8 slash commands that auto-chain secondary skills on failure, security findings, and browser issues — no manual intervention needed.
The story file is the bridge. When the planning track is done, the developer reads the story and runs /spec → /plan → /build → /review → /ship.
This repo includes a repo-local Codex marketplace at .agents/plugins/marketplace.json.
Install it locally:
codex plugin marketplace add .agents/plugins
codex plugin add avila-tek-skill-pack@avila-tek
Start a new Codex thread after installing so the skill list is reloaded.
PLANNING TRACK (Tech Lead) DEV TRACK (Developer)
══════════════════════════ ══════════════════════
[Design Doc in Lark Wiki]
│
▼
/project-context-generator ───► docs/project_context.md
│
▼
/domain-model-generator ───────► docs/domain_model.md
│
▼
/functional-spec-generator ────► Spec Funcional (Lark Wiki)
│
▼
/technical-design-document ────► docs/epics/E-XXX/tdd.md (optional)
│
▼
/epic-and-stories-generator ───► ┌─────────────────────────────────┐
│ Phase 1: epic.md │ docs/epics/E-XXX/epic.md │
│ Phase 2: stories │ docs/epics/E-XXX/stories/ │
│ │ E-XXX_S-YYY_slug/ │◄── HANDOFF
│ │ E-XXX_S-YYY_slug.md │
│ └─────────────────────────────────┘
│ │
/write-epics-and-hu-in-base ──► Lark Base │
▼
/spec ─────► spec.md
│
▼
/plan ─────► plan.md + todo.md
│
▼
/build ────► code + tests
│
▼
/review ───► code review
│
▼
/ship ─────► production
Seven sequential skills that move a Design Doc through context, domain model, spec, TDD, epics, and stories. Each skill asks clarifying questions before generating — never invents business rules.
| Command | Output artifact | Where it lives |
|---|---|---|
/project-context-generator | project_context.md | docs/ |
/domain-model-generator | domain_model.md | docs/ |
/functional-spec-generator | Spec Funcional | Lark Wiki (copy/export) |
/technical-design-document | tdd.md | docs/epics/E-XXX/ |
/epic-and-stories-generator | epic.md + story files | docs/epics/E-XXX/ + docs/epics/E-XXX/stories/ |
/write-epics-and-hu-in-base | Epics + stories synced | Lark Base |
To use the Planning Track effectively, read PLANNING.md first. It covers every skill in detail: what each one asks before generating, what each artifact contains, the rules that govern the process, and how the skills connect. The table above is a summary — the full picture is in that document.
Eight slash commands. Each one chains secondary skills automatically — you never need to invoke them manually.
npx claudepluginhub avila-tek/avila-tek-skill-packAI-powered cascading development framework with design document system and multi-agent collaboration. Breaks down projects into Features (Mega Plan), Features into Stories (Hybrid Ralph), with auto-generated technical design docs, dependency-driven batch execution, Git Worktree isolation, and support for multiple AI agents (Codex, Amp, Aider, etc.).
Specification-driven development workflow: specify → plan → tasks → implement
Complete development toolkit - documentation, PRDs, design docs, debugging, PR workflows, and planning
Spec-driven development for big features. When features get too big, plan mode gets too vague—leading to hallucinations during implementation. ShipSpec replaces vague plans with structured PRDs, technical designs, and ordered tasks that keep Claude grounded.
Document Driven Development — a structured workflow for AI-assisted software development with TDD, specs, and cross-review
AI-first engineering workflow with BDD living documentation. Lean PRD writing, Gherkin generation, and wireframe mockups for Product and Engineer roles.