feature-dev skill
탐색, 아키텍처 설계, 구현 및 품질 검토를 포함하여 새로운 기능을 구현하기 위한 구조화된 7단계 워크플로우를 실행합니다.
- GitHub 스타
- 45
- 파일
- 3
- 마지막 커밋
- 2026년 5월 31일
- 라이선스
- MIT
- 허용된 도구
- 15
feature-dev skill은 무엇을 하나요?
탐색, 아키텍처 설계, 구현 및 품질 검토를 포함하여 새로운 기능을 구현하기 위한 구조화된 7단계 워크플로우를 실행합니다.
skill의 SKILL.md에서 생성된 요약입니다.
feature-dev skill 정보
이 워크플로우는 개발자가 새로운 기능을 구현하거나 대규모 코드베이스 변경을 관리할 수 있도록 지원합니다. 초기 탐색 및 요구사항 수집부터 최종 문서화에 이르기까지 엄격한 7단계 프로세스를 따릅니다. 에이전트에게 기능 설명을 부여할 때 이 SKILL을 로드하면 아키텍처 설계나 품질 검토와 같은 중요한 단계를 누락하지 않고 구조적인 접근 방식을 보장할 수 있습니다.
이 프로세스는 높은 표준을 유지하기 위해 여러 전문 도구와 서브 에이전트에 의존합니다. 코드베이스 탐색을 위해 deep-analysis skill을 활용하며, 다양한 구현 전략을 제안하기 위해 전용 code-architect 에이전트를 실행합니다. 빌드 단계에서는 Edit tool을 사용하여 파일을 수정하고 Task tool을 사용하여 전문 code-reviewer 에이전트들을 조율합니다. 워크플로우의 마지막에는 아키텍처 결정 기록(ADR)을 생성하고 프로젝트의 CHANGELOG.md를 업데이트하여 모든 기술적 결정과 성과를 공식적으로 문서화합니다.
agent가 수행할 수 있는 작업
- 1전체 기능 구현 실행기능 설명을 제공하여 에이전트가 탐색, 설계, 코딩 및 검토를 수행하도록 안내합니다.
- 2아키텍처 설계 옵션 생성단순성, 유연성 및 기존 프로젝트 패턴을 비교할 수 있도록 여러 구현 방식을 요청합니다.
- 3다각도 코드 리뷰 수행전문 에이전트를 사용하여 새로운 코드의 정확성, 보안 및 유지보수성을 점검합니다.
skill의 SKILL.md를 기반으로 작성되었습니다. 모든 사용 사례는 해당 문서의 인용구와 대조 확인되었습니다.
feature-dev skill 설치 방법
각 명령은 skill 폴더를 클라이언트의 skills 디렉터리에 복사합니다. 클라이언트를 재시작하거나 새 세션을 시작하여 로드하세요.플러그인에 feature-dev skill 설치
/plugin marketplace add sequenzia/agent-alchemy /plugin install agent-alchemy-dev-tools@agent-alchemy
Claude Code에 feature-dev skill 설치
~/.claude/skills/feature-dev/SKILL.md
$ npx degit sequenzia/agent-alchemy/claude/dev-tools/skills/feature-dev ~/.claude/skills/feature-devClaude Code (project)에 feature-dev skill 설치
.claude/skills/feature-dev/SKILL.md
$ npx degit sequenzia/agent-alchemy/claude/dev-tools/skills/feature-dev .claude/skills/feature-devCodex에 feature-dev skill 설치
~/.agents/skills/feature-dev/SKILL.md
$ npx degit sequenzia/agent-alchemy/claude/dev-tools/skills/feature-dev ~/.agents/skills/feature-devGemini CLI에 feature-dev skill 설치
~/.gemini/skills/feature-dev/SKILL.md
$ npx degit sequenzia/agent-alchemy/claude/dev-tools/skills/feature-dev ~/.gemini/skills/feature-devClaude.ai에 feature-dev skill 설치
npx degit sequenzia/agent-alchemy/claude/dev-tools/skills/feature-dev feature-dev && zip -r feature-dev.zip feature-dev # claude.ai → Customize → Skills → + → Create skill → Upload a skill → feature-dev.zip
자동 검사
2026년 11월 16일에 실행됨전체 보고서 →아직 검증되지 않았습니다. 스킬은 점수 80, 심각한 발견 없음, 검사에 충분한 데이터가 필요합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능sequenzia/agent-alchemy/claude/dev-tools/skills/feature-dev is public and reachablegithub.com/sequenzia/agent-alchemy/tree/HEAD/claude/dev-tool ↗통과
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit 2026-05-31github.com/sequenzia/agent-alchemy/commits ↗통과
- 스크립트에 다운로드 후 실행이나 자격 증명 탈취가 없음No scripts in the skill folder통과
- SKILL.md에 숨겨진 지침 없음No override phrases, safeguard switches, credential requests or hidden charactersgithub.com/sequenzia/agent-alchemy/blob/HEAD/claude/dev-tool ↗통과
- 사전 허용 도구가 제한됨Bash lets the agent run any shell command without askinggithub.com/sequenzia/agent-alchemy/blob/HEAD/claude/dev-tool ↗결함 발견
- SKILL.md가 Agent Skills 형식을 따름Valid name and description; says when to use it; 276 linesgithub.com/sequenzia/agent-alchemy/blob/HEAD/claude/dev-tool ↗통과
SKILL.md
GitHub에서 보기Feature Development Workflow
Execute a structured 7-phase feature development workflow. This workflow guides you through understanding, exploring, designing, implementing, and reviewing a feature.
CRITICAL: Complete ALL 7 phases. The workflow is not complete until Phase 7: Summary is finished. After completing each phase, immediately proceed to the next phase without waiting for user prompts.
Phase Overview
Execute these phases in order, completing ALL of them:
- Discovery - Understand the feature requirements
- Codebase Exploration - Map relevant code areas
- Clarifying Questions - Resolve ambiguities
- Architecture Design - Design the implementation approach
- Implementation - Build the feature
- Quality Review - Review for issues
- Summary - Document accomplishments
Phase 1: Discovery
Goal: Understand what the user wants to build.
-
Analyze the feature description from
$ARGUMENTS:- What is the core functionality?
- What are the expected inputs and outputs?
- Are there any constraints mentioned?
- What success criteria can you infer?
-
Summarize your understanding to the user. Use AskUserQuestion to confirm if your understanding is correct before proceeding.
Phase 2: Codebase Exploration
Goal: Understand the relevant parts of the codebase.
-
Run deep-analysis workflow:
- Read
${CLAUDE_PLUGIN_ROOT}/../core-tools/skills/deep-analysis/SKILL.mdand follow its workflow - Pass the feature description from Phase 1 as the analysis context
- This handles reconnaissance, team planning, approval (auto-approved when skill-invoked), team creation, parallel exploration (code-explorer agents), and synthesis (code-synthesizer agent)
- Note: Deep-analysis may return cached results if a valid exploration cache exists. In skill-invoked mode, cache hits are auto-accepted — this is expected behavior that avoids redundant exploration.
- Read
-
Present the synthesized analysis to the user.
Phase 3: Clarifying Questions
Goal: Resolve any ambiguities before designing.
-
Review the feature requirements and exploration findings.
-
Identify underspecified aspects:
- Edge cases not covered
- Technical decisions that could go multiple ways
- Integration points that need clarification
- Performance or scale requirements
-
Ask clarifying questions: Use AskUserQuestion to get answers for critical unknowns. Only ask questions that would significantly impact the implementation.
If no clarifying questions are needed, inform the user and proceed.
Phase 4: Architecture Design
Goal: Design the implementation approach.
-
Load skills for this phase:
- Read
${CLAUDE_PLUGIN_ROOT}/skills/architecture-patterns/SKILL.mdand apply its guidance - Read
${CLAUDE_PLUGIN_ROOT}/../core-tools/skills/language-patterns/SKILL.mdand apply its guidance - Read
${CLAUDE_PLUGIN_ROOT}/../core-tools/skills/technical-diagrams/SKILL.mdand apply its styling rules for any Mermaid diagrams in architecture proposals
- Read
-
Launch code-architect agents:
Launch 2-3 code-architect agents (Opus) with different approaches:
Agent 1: Design a minimal, focused approach prioritizing simplicity Agent 2: Design a flexible, extensible approach prioritizing future changes Agent 3: Design an approach optimized for the project's existing patterns (if applicable)Use the Task tool with
subagent_type: "agent-alchemy-core-tools:code-architect":Feature: [feature description] Design approach: [specific approach for this agent] Based on the codebase exploration: [Summary of relevant files and patterns] Design an implementation that: - Lists files to create/modify - Describes the changes needed in each file - Explains the data flow - Identifies risks and mitigations Return a detailed implementation blueprint. -
Present approaches:
- Summarize each approach
- Compare trade-offs (simplicity, flexibility, performance, maintainability)
- Make a recommendation with justification
-
User chooses approach: Use AskUserQuestion to let the user select an approach or request modifications.
-
Generate ADR artifact:
- Read the ADR template from
${CLAUDE_PLUGIN_ROOT}/skills/feature-dev/references/adr-template.md - Create an ADR documenting:
- Context: Why this feature is needed
- Decision: The chosen approach
- Consequences: Trade-offs and implications
- Alternatives: Other approaches considered
- Determine the next ADR number by checking existing files in
internal/docs/adr/ - Save to
internal/docs/adr/NNNN-[feature-slug].md(createinternal/docs/adr/if needed) - Inform the user of the saved ADR location
- Read the ADR template from
Phase 5: Implementation
Goal: Build the feature.
-
Require explicit approval: Ask the user: "Ready to begin implementation of [feature] using [chosen approach]?" Wait for confirmation before proceeding.
-
Read all relevant files: Before making any changes, read the complete content of every file you'll modify.
-
Implement the feature:
- Follow the chosen architecture design
- Match existing code patterns and conventions
- Create new files as needed
- Update existing files using Edit tool
- Add appropriate error handling
- Include inline comments only where logic isn't obvious
-
Test if applicable:
- If the project has tests, add tests for the new functionality
- Run existing tests to ensure nothing broke
-
IMPORTANT: Proceed immediately to Phase 6. Do NOT stop here. Do NOT wait for user input. Implementation is complete, but the workflow requires Quality Review and Summary phases. Continue directly to Phase 6 now.
Phase 6: Quality Review
Goal: Review the implementation for issues.
-
Load skills for this phase:
- Read
${CLAUDE_PLUGIN_ROOT}/skills/code-quality/SKILL.mdand apply its guidance
- Read
-
Launch code-reviewer agents:
Launch 3 code-reviewer agents (Opus) with different focuses:
Agent 1: Review for correctness and edge cases Agent 2: Review for security and error handling Agent 3: Review for maintainability and code qualityUse the Task tool with
subagent_type: "code-reviewer":Review focus: [specific focus for this agent] Files to review: [List of files modified/created] Review the implementation and report: - Issues found with confidence scores (0-100) - Suggestions for improvement - Positive observations Only report issues with confidence >= 80. -
Aggregate findings:
- Collect results from all reviewers
- Deduplicate similar issues
- Prioritize by severity and confidence
-
Present findings: Show the user:
- Critical issues (must fix)
- Moderate issues (should fix)
- Minor suggestions (nice to have)
-
User decides: Use AskUserQuestion:
- "Fix all issues now"
- "Fix critical issues only"
- "Proceed without fixes"
- "I'll fix manually later"
-
If fixing: make the changes and re-review if needed.
-
IMPORTANT: Proceed immediately to Phase 7. Do NOT stop here. The workflow requires a Summary phase to document accomplishments and update the CHANGELOG. Continue directly to Phase 7 now.
Phase 7: Summary
Goal: Document and celebrate accomplishments.
-
Summarize accomplishments: Present to the user:
- What was built
- Key files created/modified
- Architecture decisions made
- Architecture diagram (Mermaid flowchart showing the implemented structure)
- Any known limitations or future work
-
Update CHANGELOG.md:
- Read the entry template from
${CLAUDE_PLUGIN_ROOT}/skills/feature-dev/references/changelog-entry-template.md - Load the
changelog-formatskill for Keep a Changelog guidelines - Create an entry under the
[Unreleased]section with:- Appropriate category (Added, Changed, Fixed, etc.)
- Concise description of the feature
- If
CHANGELOG.mddoesn't exist, create it with proper header - Add the entry to the appropriate section under
[Unreleased] - Inform the user of the update
- Read the entry template from
-
Final message: Congratulate the user and offer next steps:
- Commit the changes
- Create a PR
- Additional testing suggestions
Error Handling
If any phase fails:
- Explain what went wrong
- Ask the user how to proceed:
- Retry the phase
- Skip to next phase
- Abort the workflow
Agent Coordination
Exploration and synthesis agent coordination is handled by the deep-analysis skill in Phase 2, which uses Agent Teams with hub-and-spoke coordination. Deep-analysis performs reconnaissance, composes a team plan (auto-approved when invoked by another skill), assembles the team, and manages the exploration/synthesis lifecycle. See that skill for team setup, approval flow, agent model tiers, and failure handling details.
When launching other parallel agents (code-architect from core-tools, code-reviewer):
- Give each agent a distinct focus area
- Wait for all agents to complete before proceeding
- Handle agent failures gracefully (continue with partial results)
When calling Task tool for agents:
- Use
subagent_type: "agent-alchemy-core-tools:code-architect"(cross-plugin, from core-tools) - Use
subagent_type: "code-reviewer"for review agents (same plugin) - Code-explorer and code-synthesizer models are managed by deep-analysis
Additional Resources
- For ADR template, see references/adr-template.md
- For changelog entry format, see references/changelog-entry-template.md
이 스킬의 파일
3feature-dev skill 질문
Claude Code에 feature-dev skill을 어떻게 설치하나요?
npx degit sequenzia/agent-alchemy/claude/dev-tools/skills/feature-dev ~/.claude/skills/feature-dev를 실행합니다. Claude Code는 ~/.claude/skills(모든 프로젝트) 또는 .claude/skills(한 프로젝트)에서 skills를 로드하며, 설명이 작업과 일치할 때 skill을 사용합니다.
feature-dev skill을 사용할 수 있는 클라이언트는 무엇인가요?
Agent Skills 형식을 읽는 모든 클라이언트(Claude Code, Codex, Gemini CLI, claude.ai(ZIP으로 업로드))가 사용할 수 있습니다. skill 내 스크립트는 클라이언트가 코드 실행을 허용하는 경우에만 실행됩니다.
구현이 끝난 후 에이전트가 사용자의 입력을 기다리나요?
아니요, 에이전트는 구현이 완료되면 즉시 품질 검토(Quality Review) 단계로 진행하도록 지시받습니다.