From elixir-ash-zway
Execute an implementation plan step-by-step, following TDD principles in an Ash Framework codebase.
How this skill is triggered — by the user, by Claude, or both
Slash command
/elixir-ash-zway:ash-executeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Execute a plan created by `ash-plan`. This skill implements changes methodically, writing tests first, then implementation, validating at each step.
Execute a plan created by ash-plan. This skill implements changes methodically, writing tests first, then implementation, validating at each step.
Before executing, ensure you have:
ash-plan with:
If no plan exists, stop and use ash-plan first.
Prepare for implementation.
mix test)Follow this cycle for each feature/change in the plan:
usage-rules or hex-docs-search.Move to the next test case in the plan. Repeat Steps A-C until all test cases pass.
After all implementation steps are complete:
[x].Always prefer Ash constructs:
| Instead of... | Use... |
|---|---|
| Raw Ecto queries | Ash actions (read, create) |
| Custom validation functions | Ash validations/changes |
| Manual authorization checks | Ash policies |
| Computed fields in queries | Ash calculations |
| Standalone GenServers | Ash resources with actions |
If something goes wrong during execution:
usage-rules or hex-docs-search for guidance.If during execution you discover:
Do not silently deviate. Inform the user and get approval before changing course.
After completing each major step, report progress:
```markdown ✅ Step 1: Created test for user registration ✅ Step 2: Implemented User.register action ⏳ Step 3: Create test for email validation (in progress) ⬚ Step 4: Implement email validation change ⬚ Step 5: Run full test suite ```
This keeps the user informed and creates a clear audit trail.
npx claudepluginhub jusi-dev/dev-marketplace --plugin elixir-ash-zwayExecutes Elixir/Phoenix plan tasks with progress tracking, mix compile/test verification after each step, and resume support via --continue or --from after /phx:plan.
Executes scope-aware implementation with TDD and quality gates, scaling from inline plans for small changes to full multi-task workflows for larger work.
Executes implementation tasks from docs/plan/plan.md using TDD workflow, commits changes via git, verifies hooks, and updates progress. Use after /plan in build pipeline.