- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add waynesutton/builder-skills --skill avoid-feature-creep -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add waynesutton/builder-skills --skill avoid-feature-creep -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add waynesutton/builder-skills --skill avoid-feature-creep -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add waynesutton/builder-skills --skill avoid-feature-creep -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/waynesutton/builder-skills/tree/HEAD/skills/avoid-feature-creep게시자 제공
The request sets the scope. Everything the diff contains should trace back to a sentence in the ask. Anything else is a suggestion, not a change.
Build what was asked. Not what would be nice, not what a senior engineer would also do, not what the codebase "should" have. If a line of the diff cannot be justified by the request, it does not belong in the diff.
This applies to product scope and to code scope. A PRD that grows past its problem statement has the same disease as a bug fix that ships with a refactor.
Stop when you notice any of these:
Each of these might be a good idea. None of them are in scope unless the user says so.
Suggestions heading, one line eachOut of scope with a one line reasonprds/ folder, append to the relevant PRD's Out of scope sectionSuggestions are cheap to write and free to ignore. Unrequested code costs review time, adds bugs, and blurs what the change was for.
Every feature request has a source: a PM, an exec, a user, a developer scratching an itch, or an AI coding agent. Treat them all the same way. Log the request, weigh it against the current scope, and defer it unless it solves the problem the work was started for.
AI agents are stakeholders now. They have opinions and they push. Common agent driven creep:
If you are the agent, catch yourself doing this and move it to the suggestions list. If you are working with an agent, state the scope at the start of the session and treat its extras like any other stakeholder ask.
Before adding anything, ask:
If the first answer is no, it goes in suggestions.
Request: "Add a deletedAt field to tasks and hide deleted tasks from the list query."
Before, the creeping version:
deletedAt to the schemaby_user_and_deleted indexlist to use the indexsoftDelete, restore, and purgeDeleted mutationslist to listActive and updated three call sitesshowDeleted argument "for the admin view later"After, the scoped version:
deletedAt: v.optional(v.number()) to the schemalist at it so deleted rows never loadSummary sent with the change:
Done: deletedAt field and list query now skips deleted tasks.
Suggestions
- A softDelete mutation to set deletedAt (nothing sets it yet)
- A restore mutation
- A cron to purge rows older than 30 days
- An admin flag on list to include deleted rows
Two lines of diff answered the request. Four lines of suggestions preserved every idea. The user decides what happens next.
A PRD earns each section by pointing back to its problem statement. When a PRD grows:
Out of scope with one reason each.Suggestions in the summary or Out of scope in the PRDKeeps a change scoped to what was asked. Flags extra features, refactors, and 'while we are here' edits, and moves them to a suggestions list instead of the diff. Use when a request is small and the a
---name: avoid-feature-creepdescription: Keeps a change scoped to what was asked. Flags extra features, refactors, and 'while we are here' edits, and…---# skills/avoid-feature-creep/SKILL.md개요
Keeps a change scoped to what was asked. Flags extra features, refactors, and 'while we are here' edits, and moves them to a suggestions list instead of the diff. Use when a request is small and the agent is about to expand it, when a PRD grows beyond its problem statement, or when the user says 'just do what I asked'.
FAQ
게시자에게서 skills/avoid-feature-creep/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/waynesutton/builder-skills에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.