feature-dev
Guided feature development: codebase exploration, clarifying questions, competing architectures, implementation and parallel quality review.
Reference
| Field | Value |
|---|---|
| Name | feature-dev |
| Version | 1.0.0 |
| Category | Development |
| Licence | Not declared |
| Source | catalog/navin/builtin_plugins/feature-dev/plugin.json |
| README | catalog/navin/builtin_plugins/feature-dev/README.md |
| Digest | sha256:cedb55f6a33c6ae4692f6624a94b4c56b4b37ba5d167f91d84cdb2f310c0559e |
| plugin.json | agents, category, commands, description, name, skills, steps, version |
Commands
| Name | Arguments | Description |
|---|---|---|
/feature-dev | Optional feature description | Guided feature development - explore the codebase, clarify, design, build and review |
Agents
| Name | Tools | Model | Description |
|---|---|---|---|
code-explorer | read_file, grep, find_files, list_dir, code_index, metagraph, lsp, web_fetch, web_search | - | Traces how an existing feature works - entry points, execution paths, architecture layers, patterns and dependencies - to prepare new development. Use when a feature must be understood end to end before it is changed or extended. |
code-architect | read_file, grep, find_files, list_dir, code_index, metagraph, lsp, web_fetch, web_search | - | Designs the architecture of a feature from the patterns and conventions already in the codebase, and delivers a complete implementation blueprint - files to create or change, component design, data flow and build order. Use when a feature needs a decided design before coding. |
code-reviewer | read_file, grep, find_files, list_dir, code_index, lsp, code_review, web_fetch, web_search | - | Reviews code for bugs, logic errors, security flaws, quality problems and project-convention breaches, scoring each finding for confidence and reporting only the high-priority ones. Use when code was written or changed and needs a review before it is merged. |
Skills
| Name | Description |
|---|---|
| fullstack-dev | Build, run, and debug frontend, backend, and database projects end to end in the workspace (plan, investigate, code, execute, verify). |
| test-generator | Generate and run unit, API, and E2E tests (including Playwright) that match project conventions. |
| code-reviewer | Review code changes for bugs, security issues, regressions, and maintainability. |
Hooks, MCP servers and settings
plugin.json declares no hook, no MCP server and no setting: the plugin is made of the components above only.
Workflow
| Step | Use |
|---|---|
| start a new feature | /feature-dev |
| understand the existing code | agent:code-explorer |
| design the architecture | agent:code-architect |
| implement | skill:fullstack-dev |
| write the tests | skill:test-generator |
| review the result | agent:code-reviewer |
Enable it in a project
Activating feature-dev creates 8 activations in the project: the plugin itself, 3 skills, 1 command and 3 agents. Removing the plugin activation removes them all.
curl -X POST <control-plane-url>/v1/projects/<project>/navin-library/activations \
-H "Authorization: Bearer <token>" -H "Content-Type: application/json" \
-d '{"kind": "plugin", "name": "feature-dev"}'
<project>: id or slug of the project. <token>: API key with the editor role on the project.
client.navin_library.activate("<project>", "plugin", "feature-dev")