Agent skill

Feature Dev

by mobazha in mobazha/mobazha-unified

Guided 7-phase feature development workflow with codebase exploration, architecture design, and quality review.

MPL-2.0Auto-check passed

Install Feature Dev

skills CLI
$ npx skills add mobazha/mobazha-unified --skill feature-dev -a claude-code

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

GitHub CLI
$ gh skill install mobazha/mobazha-unified 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/mobazha/mobazha-unified.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/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
165
Token cost
~458 tokens
SKILL.md length
151 words
Files
1
Skills in repo
29
Repo updated
First seen
Licence
MPL-2.0

At a glance

Guided 7-phase feature development workflow with codebase exploration, architecture design, and quality review.

  • Works in 3 steps: 创建包含 7 个阶段的 todo 列表 → 如需求不清晰,向用户确认 → 总结理解并与用户确认
  • The user wants to implement a new feature
  • SKILL.md covers 核心原则, 阶段 1:需求理解, 阶段 2:代码探索 and 阶段 3:澄清问题, plus 4 more sections
  • Calls pnpm

What it does

Feature Dev is an agent skill from mobazha/mobazha-unified. Guided 7-phase feature development workflow with codebase exploration, architecture design, and quality review. Use when the user wants to implement a new feature, build a new module, or asks for structured development workflow, "开发功能", "新功能", "功能开发", "实现功能", "添加功能".

Its SKILL.md is about 460 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Open-source commerce frontend for storefronts, marketplaces, checkout, and seller management. The licence is MPL-2.0.

When your agent uses it

  • The user wants to implement a new feature
  • Build a new module
  • Asks for structured development workflow

Example prompts

  • “/feature-dev”

Workflow steps

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

  1. 创建包含 7 个阶段的 todo 列表
  2. 如需求不清晰,向用户确认
  3. 总结理解并与用户确认

What it can do on your machine

Read from SKILL.md and the folder at commit 156c699. 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

    Shell commands in SKILL.md call:

    • pnpm

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

  • Network

    No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.

    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 458 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 151 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~458

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 mobazha/mobazha-unified at commit 156c699, republished under its MPL-2.0 licence (© mobazha). 151 words, ~458 tokens.

Download SKILL.mdSave it as .claude/skills/feature-dev/SKILL.md (or your agent's skills folder).
name
feature-dev
description
Guided 7-phase feature development workflow with codebase exploration, architecture design, and quality review. Use when the user wants to implement a new feature, build a new module, or asks for structured development workflow, "开发功能", "新功能", "功能开发", "实现功能", "添加功能".

功能开发工作流

Mobazha Unified 项目的 7 阶段系统化功能开发方法。

核心原则

  • 先问清楚再动手 — 在设计前识别所有模糊点和边界情况
  • 先理解后行动 — 先阅读理解现有代码模式
  • 简洁优雅 — 优先可读、可维护、架构合理的代码
  • 使用 TodoWrite — 全程跟踪进度

阶段 1:需求理解

目标:明确要构建什么

  1. 创建包含 7 个阶段的 todo 列表
  2. 如需求不清晰,向用户确认:
    • 要解决什么问题?
    • 功能应该做什么?
    • 有什么约束或要求?
  3. 总结理解并与用户确认

阶段 2:代码探索

目标:理解相关的现有代码和模式

  1. 并行启动 2-3 个 code-explorer agent,各关注不同方面:
    • "查找与 [功能] 类似的功能并追踪其实现"
    • "映射 [功能领域] 的架构和抽象"
    • "分析 [现有相关功能] 的当前实现"
  2. 阅读 agent 识别的所有关键文件
  3. 向用户展示综合发现摘要

阶段 3:澄清问题

目标:填补信息缺口,解决所有模糊点

关键:此阶段不可跳过

  1. 回顾代码探索发现和原始需求
  2. 识别未明确的方面:
    • 边界情况、错误处理、集成点
    • 范围边界、设计偏好
    • 向后兼容性、性能需求
  3. 以清晰有序的列表向用户提出所有问题
  4. 等待用户回答后再继续

阶段 4:架构设计

目标:设计实现方案

  1. 并行启动 2-3 个 code-architect agent,关注不同方向:
    • 最小改动(最小变更,最大复用)
    • 整洁架构(可维护性,优雅抽象)
    • 务实平衡(速度 + 质量)
  2. 向用户展示:
    • 每个方案的简要总结
    • 权衡比较
    • 你的推荐及理由
  3. 询问用户偏好哪个方案

阶段 5:实现

目标:构建功能

未获得用户批准前不得开始

  1. 等待用户明确批准所选方案
  2. 阅读前面阶段识别的所有相关文件
  3. 按选定架构实现
  4. 严格遵循代码规范(见 .cursor/rules/)
  5. 随进度更新 todo
架构检查清单
  • 类型定义在 @mobazha/core/types/
  • 转换函数在 @mobazha/core/utils/transforms/
  • 数据获取 hooks 在 @mobazha/core/hooks/
  • UI 组件只通过 props 接收处理好的数据
  • apps/ 目录中无业务逻辑

阶段 6:质量审查

目标:确保代码质量

  1. 启动 code-reviewer agent 审查变更
  2. 汇总发现,识别最高严重度问题
  3. 向用户展示发现并询问处理方式(现在修复、稍后修复、或直接继续)
  4. 按用户决定处理问题
  5. 运行验证:
bash
pnpm validate:quick

阶段 7:总结

目标:记录完成的工作

  1. 将所有 todo 标记完成
  2. 总结:
    • 构建了什么
    • 做了哪些关键决策
    • 修改/创建了哪些文件
    • 建议的后续步骤

© mobazha, MPL-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

Just SKILL.md in .cursor/skills/feature-dev of mobazha/mobazha-unified.

Open the folder on GitHubat commit 156c699

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 skillmobazha/mobazha-unified165—~458Automated safety check: PassMPL-2.0
Explorersupabase/supabase111k—~845Automated safety check: PassApache-2.0
Write Guidevercel/next.js143k—~1.6kAutomated safety check: PassMIT
Design Guidepaperclipai/paperclip99k1 repos~3.1kAutomated safety check: PassMIT
Agent Scout Explorerruvnet/ruflo74k3 repos~1.6kAutomated safety check: PassMIT
Write Guidesremix-run/remix33k—~2.6kAutomated safety check: PassMIT

Similar skills

  • Explorer

    supabase/supabase

    Official

    Build and modify Studio Explorer surfaces, including notebooks, chats, SQL snippets, query cells, and their shared toolbar patterns.

    111k GitHub stars~845 tokensUpdated today
    DatabasesAuto-check passed
  • Write Guide

    vercel/next.js

    Official

    Generates technical guides that teach real-world use cases through progressive examples.

    143k GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Design Guide

    paperclipai/paperclip

    Paperclip UI design system guide for building consistent, reusable frontend components.

    99k GitHub starsUsed in 1 repo~3.1k tokens
    Frontend & DesignAuto-check passed
  • Agent skill for scout-explorer - invoke with $agent-scout-explorer

    74k GitHub starsUsed in 3 repos~1.6k tokens
    Auto-check passed
  • Write Guides

    remix-run/remix

    Write, rewrite, or audit Remix guide chapters in the voice of docs/guides/app/actions/docs/chapters/01-start-here.md.

    33k GitHub stars~2.6k tokensUpdated today
    Writing & ContentAuto-check passed
  • Caveman Repository Explorer

    JuliusBrussee/caveman

    A read-only explorer for cold-start orientation or failed searches that replies with nothing but file path and line range citations, keeping its reads out of main context.

    110k GitHub starsUsed in 1 repo~492 tokens
    Agent WorkflowsAuto-check passed

More from mobazha/mobazha-unified

All 29 skills in this repo
  • A11y Guide

    mobazha/mobazha-unified

    Accessibility guide for Mobazha following WCAG 2.1 AA standards including color contrast, reduced motion, ARIA patterns, keyboard navigation, focus management, and screen reader testing.

    165 GitHub stars~1.4k tokensUpdated 5 days ago
    Auto-check passed
  • API Reference

    mobazha/mobazha-unified

    Look up Mobazha backend API endpoints, request/response formats, and field mappings.

    165 GitHub stars~1.7k tokensUpdated 5 days ago
    Auto-check passed
  • Code Review

    mobazha/mobazha-unified

    Review code for quality, architecture consistency, and adherence to Mobazha project standards using confidence-based filtering.

    165 GitHub stars~464 tokensUpdated 5 days ago
    Auto-check passed
  • Code Simplifier

    mobazha/mobazha-unified

    Simplify and refine recently written code for clarity, consistency, and maintainability while preserving all functionality.

    165 GitHub stars~601 tokensUpdated 5 days ago
    Auto-check passed
  • Commit Helper

    mobazha/mobazha-unified

    Generate commit messages and run pre-commit validation following Mobazha conventions.

    165 GitHub stars~735 tokensUpdated 5 days ago
    Auto-check passed
  • Component Dev

    mobazha/mobazha-unified

    Create and modify UI components following Mobazha conventions including directory structure, spacing standards, accessibility, and testing.

    165 GitHub stars~638 tokensUpdated 5 days ago
    Auto-check passed

Questions about Feature Dev

What does Feature Dev do?

Guided 7-phase feature development workflow with codebase exploration, architecture design, and quality review. Feature Dev is an agent skill from mobazha/mobazha-unified. Guided 7-phase feature development workflow with codebase exploration, architecture design, and quality review.

When should I use Feature Dev?

Feature Dev fits situations like: the user wants to implement a new feature; build a new module; asks for structured development workflow.

How do I install Feature Dev in Claude Code?

Run `npx skills add mobazha/mobazha-unified --skill feature-dev -a claude-code`. Or copy the skill folder (.cursor/skills/feature-dev in mobazha/mobazha-unified) 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 mobazha/mobazha-unified --skill feature-dev -a codex`. Or copy the skill folder (.cursor/skills/feature-dev in mobazha/mobazha-unified) 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 mobazha/mobazha-unified --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?

Going by SKILL.md and its folder, Feature Dev needs the command-line tools its instructions call (pnpm).

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 MPL-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 458 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Feature Dev?

Skills that share tags, products or a category with Feature Dev: Explorer (supabase/supabase, 111k stars), Write Guide (vercel/next.js, 143k stars), Design Guide (paperclipai/paperclip, 99k stars) and Agent Scout Explorer (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Feature Dev?

mobazha (a GitHub organization) maintains it in mobazha/mobazha-unified, which has 165 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 3, 2026.

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