hungry-jack
Carry a substantial change from the request to a review-ready result.
Some tasks don’t fit in one tidy implementation pass. A background job might touch the database, API, worker, and UI. Hungry Jack coordinates the focused skills so that the work gets built in slices and checked as a whole.
When I’d use it
Use it for substantial work across systems: payments, authorization, jobs, integrations, or architectural changes. For a contained feature, implement-feature is usually enough.
Before you start
Install the companion bundle below. Describe the outcome and constraints. You can set optional effort to snack, balanced, feast, or banquet; balanced is the default. More effort does not waive required checks or approval for high-risk work.
Install it. Then give it a task.
Run this in your project’s terminal. Choose your coding agent in the installer, then start a new agent session if it needs one to discover the skill.
$ npx skills add akdevsaha-dev/factory-skills --skill hungry-jack plan-change implement-feature verify-work simplify-code review-changes reflectThis installs Hungry Jack with its companion workflows. The bundle avoids a missing-skill interruption partway through a task; reflect is optional.
Once installed, send a prompt like the ones below to your agent. These are example requests to adapt to your own project, not terminal commands or recorded results.
If slash commands aren’t available in your agent, write “Use the hungry-jack skill to…” and describe the same task.
New to skills? Start with the installation walkthroughWhat happens next
- Inspects the task, scope, and risk.
- Plans when needed and hands slices to implement-feature.
- Verifies the full change, then simplifies or reviews where justified.
- Fixes confirmed issues within bounded loops and gives an evidence-based handoff.
A few ways to ask
5 examplesCopy the one closest to your task. Replace names, paths, dates, and refs with ones that exist in your project.
Coordinate a substantial feature
› /hungry-jack add refunds to orders. Use our existing payment provider and order permissions. Support partial refunds and duplicate-request protection.Money movement is high-risk. Expect a plan approval step before implementation.
Move work into a job
› /hungry-jack --effort feast move invoice generation to a background job. Keep the current invoice output and show users pending, completed, and failed states.Feast spends more optional effort on architecture, regression checks, and independent review.
Set a tight scope
› /hungry-jack --effort snack add a bulk archive action to the project list. Reuse the existing archive behavior and report if the task is broader than it looks.Snack reduces optional process. It still keeps the work and verification the task requires.
Explore failure modes
› /hungry-jack --effort banquet add organization-level permissions. Existing personal accounts must keep working. Plan the migration and tenant-isolation checks before editing.Banquet goes deeper on failure modes and security boundaries; it is not a promise that every task needs that much process.
Describe the business outcome
› Use hungry-jack to let customers track a long-running import. Include progress, failure details, and a safe retry. Reuse our current queue and upload flow.You can describe the outcome without knowing the implementation slices.
What to look for in the result
A report of the implementation, important decisions, checks, skipped checks, risks, and readiness for review. Missing required companions stop the workflow. It does not commit, push, merge, or deploy unless asked.
A thing worth watching
Start balanced. Turn effort up because the change deserves deeper work, not because the longest process sounds safest. Reflect is optional and only runs when a demonstrated failure calls for it.
Use it with
Build a workflow you can repeat.
Follow the step-by-step guide to working with agents.