New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Feature Dev

by HorizonRobotics in HorizonRobotics/RoboOrchardLab

Guided feature development with codebase understanding and architecture focus.

Apache-2.0Auto-check passedDevelopment

Install Feature Dev

skills CLI
$ npx skills add HorizonRobotics/RoboOrchardLab --skill feature-dev -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install HorizonRobotics/RoboOrchardLab feature-dev --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/HorizonRobotics/RoboOrchardLab.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/feature-dev .claude/skills/feature-dev && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
feature-dev
GitHub stars
173
Token cost
~797 tokens
SKILL.md length
379 words
Files
2 (incl. references)
Skills in repo
8
Repo updated
First seen
Licence
Apache-2.0

At a glance

Guided feature development with codebase understanding and architecture focus.

  • Works in 7 steps: Discovery: understand the request and… → Codebase exploration: map relevant… → Clarifying questions: resolve material… → …
  • Implementing a non-trivial feature that benefits from structured discovery
  • SKILL.md covers Read Next, Role, Core Principles and Workflow Summary, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Feature Dev is an agent skill from HorizonRobotics/RoboOrchardLab. Guided feature development with codebase understanding and architecture focus. Use when implementing a non-trivial feature that benefits from structured discovery, exploration, architecture comparison, implementation, and review.

Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/phase-workflow.md`).

It sits in Development. The licence is Apache-2.0.

When your agent uses it

  • Implementing a non-trivial feature that benefits from structured discovery
  • Architecture comparison

Example prompts

  • “/feature-dev”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Discovery: understand the request and constraints.
  2. Codebase exploration: map relevant implementation patterns.
  3. Clarifying questions: resolve material ambiguity before designing.
  4. Architecture design: compare viable approaches and choose one.
  5. Implementation: build the approved or obvious approach.
  6. Quality review: run risk-appropriate review, validation, and Cleanup Gate.
  7. Summary: report decisions, changed files, validation, and residual risks.

What it can do on your machine

Read from SKILL.md and the folder at commit 221ec0e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Feature Dev loads about 797 tokens when it runs, and up to ~2.6k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 379 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~797
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from HorizonRobotics/RoboOrchardLab at commit 221ec0e, republished under its Apache-2.0 licence (© HorizonRobotics). 379 words, ~797 tokens.

Download SKILL.mdSave it as .claude/skills/feature-dev/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
feature-dev
description
Guided feature development with codebase understanding and architecture focus. Use when implementing a non-trivial feature that benefits from structured discovery, exploration, architecture comparison, implementation, and review.

Use this skill to coordinate non-trivial feature work from discovery through implementation, review, validation, and summary.

Before running this workflow, read:

  • references/phase-workflow.md

Use the sub-skills in this directory only when their phase applies:

  • code-explorer: deep codebase tracing and implementation analysis
  • code-architect: architecture design and implementation blueprinting
  • code-reviewer: high-signal review for correctness and project fit

Role

This parent skill is the orchestration layer. Keep it focused on routing, phase selection, and handoff between sub-skills. Concrete execution details belong in the phase workflow reference or in the smallest applicable sub-skill.

Core Principles

  • Understand the codebase before changing it.
  • Ask concrete clarifying questions when behavior, scope, compatibility, or integration points are underspecified.
  • Read files surfaced by exploration or design passes before making architectural claims.
  • Prefer simple, maintainable designs grounded in repository patterns.
  • Track progress with a todo list when the work spans multiple steps.
  • Compress the workflow for trivial tasks, but preserve the same reasoning discipline.

Workflow Summary

The detailed actions, examples, and review rules live in references/phase-workflow.md. The phase order is:

  1. Discovery: understand the request and constraints.
  2. Codebase exploration: map relevant implementation patterns.
  3. Clarifying questions: resolve material ambiguity before designing.
  4. Architecture design: compare viable approaches and choose one.
  5. Implementation: build the approved or obvious approach.
  6. Quality review: run risk-appropriate review, validation, and Cleanup Gate.
  7. Summary: report decisions, changed files, validation, and residual risks.
Show full SKILL.md (149 more words)Show less

Delegation Rules

  • Use code-explorer for broad or unfamiliar areas before designing.
  • Use code-architect when multiple credible architecture choices exist.
  • Use code-reviewer for non-trivial implementation review or explicit review loops.
  • Default to at most one active delegated reviewer per review round. Treat architecture, correctness, simplicity, and project conventions as review dimensions that one reviewer can cover together.
  • In a review loop, keep the current reviewer only long enough to verify fixes for its own findings, then start the next full-scope round with a fresh reviewer.
  • Use parallel reviewers within one round only when the user explicitly requests them or a concrete high-risk scope justifies independent review.
  • After delegated review, the main agent still owns consolidation, validation, and final handoff quality.

When Not To Use

This workflow is usually overkill for:

  • one-line bug fixes
  • trivial refactors
  • clearly scoped edits in a single file
  • urgent hotfixes where architecture comparison adds no value

© HorizonRobotics, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in .agents/skills/feature-dev of HorizonRobotics/RoboOrchardLab.

  • SKILL.md
  • references/phase-workflow.md

Open the folder on GitHubat commit 221ec0e

Compare with similar skills

Feature Dev next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Feature Dev compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Feature Dev this skillHorizonRobotics/RoboOrchardLab173—~797Automated safety check: PassApache-2.0
Vercel Composition Patternssupabase/supabase111k59 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 59 repos~726 tokens
    DevelopmentAuto-check passed

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from HorizonRobotics/RoboOrchardLab

All 8 skills in this repo

  • Codereview Family

    HorizonRobotics/RoboOrchardLab

    Structured code review family for explicit heavy review requests and architecture-sensitive review/evaluation requests.

    173 GitHub stars~724 tokensUpdated 13 days ago
    Auto-check passed

  • Architecture Review

    HorizonRobotics/RoboOrchardLab

    Review local code, diffs, modules, directories, or design changes for consequential architecture issues when the user explicitly asks for architecture review, when an upstream review routes…

    173 GitHub stars~1k tokensUpdated 13 days ago
    Auto-check passed

  • Prmr Codereview

    HorizonRobotics/RoboOrchardLab

    Review a GitHub PR or GitLab MR when the task is a PR/MR review or comment flow.

    173 GitHub stars~961 tokensUpdated 13 days ago
    Auto-check passed

  • Code Architect

    HorizonRobotics/RoboOrchardLab

    Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create or modify, component…

    173 GitHub stars~750 tokensUpdated 13 days ago
    Auto-check passed

  • Code Explorer

    HorizonRobotics/RoboOrchardLab

    Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development.

    173 GitHub stars~721 tokensUpdated 13 days ago
    Auto-check passed

  • Code Reviewer

    HorizonRobotics/RoboOrchardLab

    Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that…

    173 GitHub stars~1.2k tokensUpdated 13 days ago
    Auto-check passed

Categories

Questions about Feature Dev

What does Feature Dev do?

Guided feature development with codebase understanding and architecture focus. Feature Dev is an agent skill from HorizonRobotics/RoboOrchardLab. Guided feature development with codebase understanding and architecture focus.

When should I use Feature Dev?

Feature Dev fits situations like: implementing a non-trivial feature that benefits from structured discovery; architecture comparison.

How do I install Feature Dev in Claude Code?

Run `npx skills add HorizonRobotics/RoboOrchardLab --skill feature-dev -a claude-code`. Or copy the skill folder (.agents/skills/feature-dev in HorizonRobotics/RoboOrchardLab) into .claude/skills/feature-dev in your project. Claude Code loads it when a task matches its description.

How do I install Feature Dev in Codex?

Run `npx skills add HorizonRobotics/RoboOrchardLab --skill feature-dev -a codex`. Or copy the skill folder (.agents/skills/feature-dev in HorizonRobotics/RoboOrchardLab) into .agents/skills/feature-dev in your project. Codex loads it when a task matches its description.

Can I use Feature Dev in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HorizonRobotics/RoboOrchardLab --skill feature-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/feature-dev, .gemini/skills/feature-dev, .github/skills/feature-dev and .opencode/skills/feature-dev in your project.

What does Feature Dev need to run?

SKILL.md names no scripts, command-line tools or credentials: Feature Dev is instructions for the agent only.

Does Feature Dev access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Feature Dev safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Feature Dev use?

Feature Dev is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Feature Dev use?

About 797 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.

What are the alternatives to Feature Dev?

Skills that share tags, products or a category with Feature Dev: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Feature Dev?

HorizonRobotics (a GitHub organization) maintains it in HorizonRobotics/RoboOrchardLab, which has 173 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on September 24, 2026.

Source: HorizonRobotics/RoboOrchardLab on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.