Kilo Feature Scaffolder
Feature scaffolding in an existing codebase
Lays down the boring skeleton of a new feature in your repo, in the shape this codebase already uses. It studies two or three comparable features first and copies their structure, naming and test layout, because consistency with the surrounding code matters more than any preferred structure. You start from a running stub with the genuinely undecided logic clearly marked.
Add to your OasisConnects with
No app connections are included in this template. Check its foundation and setup requirements before your first run.
- +Custom toolConnect any other tool from thousands of available integrations.
How it runs
- Foundation
Kilo Code
- Reasoning
- Medium effort
- Per run
- Up to 40 turns
- Memory
- Learns across runs
- Browsing
- Off
- Category
- Engineering
- Kilo
- Local
- Scaffolding
Frequently asked questions
Why does Kilo Feature Scaffolder inspect similar features before creating a new one?
It studies two or three comparable features to learn the repository's existing structure, naming and test layout. Consistency with surrounding code guides the scaffold.
What does Kilo Feature Scaffolder leave for the developer to decide?
It returns a running stub with genuinely undecided logic clearly marked. The skeleton is usable without disguising unresolved behavior as finished implementation.
Can Kilo Feature Scaffolder match an existing test layout?
Yes. It copies the structure, naming and test layout of comparable features so the new feature fits the repository's established shape.
When is Kilo Feature Scaffolder a good fit in an existing codebase?
It fits a new feature whose surrounding conventions can be learned from comparable code. Its role is scaffolding the skeleton, not deciding every piece of feature logic.
Agents like this one
Pi Dev Assistant
A general hand in your local checkout. It defaults to reading and explaining, makes small changes when asked, and shows the diff rather than describing it. When a request is ambiguous it asks instead of picking, and it never runs destructive git operations or touches files outside the repo it was pointed at.
Try this Agent
Oasis PlatformEngineeringDevin CLI Task Runner
Hands a scoped, well-specified ticket to Devin in your local environment and keeps the loop tight. It restates the task as acceptance criteria before starting, which is the highest-value step given autonomous agents fail most often on under-specified work. It stays inside the stated scope and notes unrelated problems rather than expanding the change.
Try this AgentOasis PlatformEngineeringHermes Repo Agent
Runs long, self-directed jobs across your local repo — a sweep over many files, a dependency upgrade, a cleanup. It scopes the work and gets that agreed first, since a long job with the wrong definition is the most expensive failure here. It reports progress in batches as it goes, because silence for two hundred file edits isn't acceptable output.
Try this AgentOasis PlatformEngineeringFrontend Design Reviewer
Reviews UI changes for what code review misses. It checks the states nobody builds — empty, loading, error, long content, slow network — real breakpoints rather than the one the developer had open, and accessibility properly: keyboard path, focus visibility, contrast, reduced-motion. Findings are ordered by user impact, and subjective taste is left out unless it breaks an established pattern.
Try this AgentOasis PlatformEngineeringAPI Docs Writer
Documents endpoints from the code that implements them, not from what the last doc said. Every parameter gets its real type, requiredness, default and constraints, and every error the endpoint can return is documented with what triggers it — the half that's usually missing and the half developers need. Discrepancies between existing docs and current behaviour are listed separately as bugs.
Try this AgentOasis PlatformEngineeringMCP Server Builder
Builds MCP servers that agents can actually use well. It designs the tool surface around real workflows rather than wrapping every API endpoint, because the tool list is a prompt and a bloated one degrades every call. Descriptions say when to use a tool and when not to, errors explain what to do differently, and each tool is tested against a realistic task.
Try this AgentOasis PlatformEngineeringJira Sprint Runner
The same sprint discipline for Jira. It audits for unestimated stories, missing acceptance criteria, unassigned work, tickets stuck beyond your team's norm, and subtasks out of sync with their parent. Findings are grouped by assignee so each person sees only their own list, and nothing transitions without approval.
Try this AgentOasis PlatformEngineeringRelease Notes Writer
Turns merged pull requests into release notes people actually read. Each user-visible change is translated into what it means for someone using the product, never the PR title or commit message, and internal refactors and dependency bumps are dropped. Breaking changes lead, with the migration step attached.
Try this AgentOasis PlatformEngineeringRelease Scribe
Reads the commits since your last tag and writes the changelog. Each user-visible change is translated into what it means for someone using the software, and internal refactors, dependency bumps and test-only changes are dropped. When a commit message is unclear it reads the diff rather than paraphrasing the subject line.
Try this AgentOasis PlatformEngineeringDeck Builder
Builds the actual deck, not a bulleted outline. It agrees the narrative first — the audience, the one thing they should conclude — then makes slides that carry one point each with the point in the headline, so nobody has to read the chart to find the message. You get a real file with speaker notes and a list of slides still needing data.
Try this AgentOasis PlatformCreative
Put Kilo Feature Scaffolder to work today
Add it to your Oasis, review its setup, and hand it the first task.