full
FeaturedDeliver a large, cross-domain Phoenix feature or complete end-to-end system through planning, implementation, verification, and review. Use when several coordinated workflows or contexts must ship together. NOT for an existing plan; use /phx:work.
Install
Quality Score: 94/100
Skill Content
Details
- Author
- oliver-kriska
- Repository
- oliver-kriska/claude-elixir-phoenix
- Created
- 5 months ago
- Last Updated
- yesterday
- Language
- Python
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
plan-feature
Engineering-planning router for an already-designed feature. Given a feature whose SPEC product half is not marked `designed`, STOPS and redirects to `/design-feature <slug>` — no bypass flag. Given a designed feature, a GitHub issue #N (issue → scoped product half, satisfying capability closure), or an already-scoped slug/SPEC (straight to engineering-half scaffolding), routes to the right internal step, then ensures the roadmap entry and prints the next step. Force a path with flags to skip detection; `--next` plans the next `defined` feature from the roadmap. On Claude Code and want hand-tuned per-skill model/effort tiers? Install the `#claude` branch instead (`npx skills add gtrabanco/agentic-workflow#claude`) — see the README. This branch is model-agnostic: the skill inherits whatever model and effort your agent session is already using. Triggers: "plan a feature", "plan the feature from issue N", "plan the next roadmap feature", "scaffold feature NN", "create SPEC and TASKS for NN".
feature
End-to-end feature workflow around the agent — spec by interview, a plan of 2–5-minute tasks, test-first execution with checkpoint commits, then an evidence-gated finish. Effort-scaled: a one-sentence diff skips straight to implementation; a real feature gets spec.md → plan.md → task-by-task TDD, with all state in out/dev/<change>/ so any later session resumes at the first unchecked task. Human-in-the-loop: the spec and the plan are approved (and editable) before any code is written, and nothing ships without the done gate. Use when the user wants to build, add, or implement a feature or start non-trivial coding work — e.g. "/feature add rate limiting", "implement X", "build a Y that Z", "resume the <change> feature". For fixing something broken use bugfix; for just the end-of-session shipping gate use done; for this whole loop end-to-end without approval stops, suggest the user run /autopilot (explicit invocation only).
drive-plan
Drive a multi-phase implementation plan to completion through a Comment.io Plan/worklog or local Markdown plan. Uses phases as execution organization, not automatic gates; validates focused deltas, invokes bounded risk-scaled review at delivery-slice or changed-invariant boundaries, keeps the plan current, and steers only on real decisions. Invoke as `$drive-plan` / `/drive-plan`, or when asked to execute a phased plan autonomously. Works identically under Codex and Claude Code.