implement-feature
Add a feature without making the codebase feel like two different projects.
This is the one I’d start with. Give it a concrete change in a project that already exists. It looks for a similar feature, follows that path through the code, and builds the new thing in the same style.
When I’d use it
Use it for a contained feature or behavior change: an export, a filter, an endpoint, or a missing error state. If the work spans several systems and needs coordination, use hungry-jack.
Before you start
Open the project in your agent. Know what should happen when the feature works, and what should happen when it fails. You don’t need to know which files to edit.
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 implement-featureOnce 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 implement-feature skill to…” and describe the same task.
New to skills? Start with the installation walkthroughWhat happens next
- Finds the code your request refers to and traces the nearest existing example.
- Turns the request into observable behavior, including failure cases.
- Implements the change using the project’s patterns and reusable code.
- Runs relevant checks, reviews the diff, and reports the evidence.
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.
Export a filtered list
› /implement-feature add CSV export to invoices. Export only the invoices matching the current filters. Reuse the existing export format if there is one.Giving the filter behavior prevents a common mismatch: exporting everything when the screen shows a subset.
Handle a failed request
› /implement-feature add loading, empty, and error states to the fetching views. Follow ProjectsView and reuse its components. Include a retry action for failed requests.Name an existing example when you know one. Otherwise let the agent find it.
Add a search control
› /implement-feature add search by project name to the projects list. Keep the search in the URL so I can share the filtered view. Preserve pagination.The URL and pagination requirements make the expected behavior explicit.
Extend an endpoint
› /implement-feature add a status filter to the existing orders endpoint. Keep the current response shape and pagination behavior. Reject unknown statuses using the existing error format.Say which contracts must stay stable, especially when other code calls the endpoint.
Use plain language
› Use the implement-feature skill to add a clear confirmation before archiving a project. Match the existing destructive-action dialogs and preserve the current permission checks.Slash commands are convenient, but mentioning the installed skill in plain words works too.
What to look for in the result
A focused diff, the important decisions, checks that actually ran, and anything still unverified. High-risk changes pause for plan approval before editing.
A thing worth watching
“Make the app better” leaves too much undecided. Start with one change you can describe and review. Don’t turn a small feature into a request to refactor the whole project.
Use it with
Build a workflow you can repeat.
Follow the step-by-step guide to working with agents.