Guided feature development with codebase understanding and architecture focus
NewMaintained
Automatic
◆Coding pack
Last verified 8/3/2026
What it changes
3 of 25 test cases passed with the skill.
Pass-rate lift
—
Tokens
+45%
Agent turns
0%
Response time
+8%
Model gemini-3.6-flashMeasured 8/3/2026v13 of 25 cases passed with skill · 7 comparable
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 7 comparable cases; this report requires 8.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
The agents have finished exploring the codebase for the two-factor authentication feature. Here is their summary. Please proceed.
What was checked, without and with the skill
Checked
Without skill
With skill
The response uses the TodoWrite tool to mark the current phase as complete.
Missed
Passed
The response does not instruct the launch of code-architect agents.
Passed
Passed
case-16 · gemini-3.6-flash · 8/3/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md120 lines4 files
Feature Development
You are helping a developer implement a new feature. Follow a systematic approach: understand the codebase deeply, identify and ask about all underspecified details, design elegant architectures, then implement.
Core Principles
Ask clarifying questions: Identify all ambiguities, edge cases, and underspecified behaviors. Ask specific, concrete questions rather than making assumptions. Wait for user answers before proceeding with implementation. Ask questions early (after understanding the codebase, before designing architecture).
Understand before acting: Read and comprehend existing code patterns first
Read files identified by agents: When launching agents, ask them to return lists of the most important files to read. After agents complete, read those files to build detailed context before proceeding.
Simple and elegant: Prioritize readable, maintainable, architecturally sound code
Use TodoWrite: Track all progress throughout
Phase 1: Discovery
Goal: Understand what needs to be built
Initial request: $ARGUMENTS
Actions:
Create todo list with all phases
If feature unclear, ask user for:
What problem are they solving?
What should the feature do?
Any constraints or requirements?
Summarize understanding and confirm with user
Phase 2: Codebase Exploration
Goal: Understand relevant existing code and patterns at both high and low levels
Actions:
Launch 2-3 code-explorer agents in parallel. Each agent should:
Trace through the code comprehensively and focus on getting a comprehensive understanding of abstractions, architecture and flow of control
Target a different aspect of the codebase (eg. similar features, high level understanding, architectural understanding, user experience, etc)