evolve-feature-classify
Capture, classify, and scope new requirements to ensure consistent architectural evolution.
Install
mkdir -p .claude/skills/evolve-feature-classify && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10524" && unzip -o skill.zip -d .claude/skills/evolve-feature-classify && rm skill.zipInstalls to .claude/skills/evolve-feature-classify
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Capture the new feature/requirement, classify the change type, identify the entry point document, write new content, and determine cascade scopeKey capabilities
- →Capture new features, requirements, or constraints
- →Classify changes into predefined types
- →Identify the correct entry point document for new content
- →Write new content at the appropriate specification depth
- →Determine the scope of cascading updates to downstream layers
How it works
The skill captures the new item, classifies it, identifies the entry point document, writes content at the correct spec depth, and then determines which downstream layers require updates.
Inputs & outputs
When to use evolve-feature-classify
- →Classifying feature requests
- →Defining technical constraints
- →Scoping architectural changes
About this skill
Evolve Feature — Classify
Capture the user's new feature, requirement, or constraint. Classify it, identify the correct entry point document, write the new content at proper spec depth, and determine which downstream layers need updating.
Prerequisite:
.memory/wiki/specs/ideation/ideation-index.mdmust exist. If not → STOP: run/ideatefirst.
1. Capture the new thing
Ask the user to describe what they want to add. Accept free-form input or @file.
If @file → read and extract key additions. If free-form → brief clarifying questions only (NOT a full /ideate interview).
2. Classify the change
Read .agents/skills/brainstorming/SKILL.md and follow its methodology.
Present the classification menu:
What type of change is this?
[1] New feature — entirely new capability
[2] New requirement on existing feature — additional constraint/behavior/criteria
[3] New technical constraint — non-functional requirement affecting architecture
[4] Scope correction — misunderstanding or underspecification that needs fixing
STOP — do not proceed until the user selects.
3. Identify the entry point document
| Classification | Entry Point Document |
|---|---|
| [1] New feature | .memory/wiki/specs/ideation/ideation-index.md + fractal tree placement (Step 4) |
| [2] New requirement | The IA shard that owns the affected domain (read .memory/wiki/specs/ia/index.md to find it) |
| [3] New technical constraint | .memory/wiki/specs/[dated]-architecture-design.md |
| [4] Scope correction | Ask the user which document contains the misunderstanding |
4. Write new content at the entry point
Read .agents/skills/technical-writer/SKILL.md for clarity standards.
Read .agents/skills/prd-templates/references/evolution-layer-guidance.md → Entry Point Writing Depth section for the entry point layer. Follow its writing checklist for the identified layer.
Inline ambiguity check: Before presenting to user, apply Micro Ambiguity Check from .agents/skills/session-continuity/SKILL.md — walk each element, fix any gaps where an implementer would need to guess.
Present the written content to the user.
STOP — do not proceed until the user approves.
5. Determine cascade scope
| Entry Point | Cascade Layers (in order) |
|---|---|
| Vision | Architecture → IA → BE → FE → Phase plan |
| Architecture | IA → BE → FE → Phase plan |
| IA shard | BE spec → FE spec → Phase plan |
| BE spec | FE → Phase plan |
| Scope correction | All layers below the corrected document |
Check each downstream layer for existing content. Only layers with existing content need updating.
Report: "These layers have existing content that will need updating: [list]."
If no downstream layers have content: "No downstream layers have existing content — incorporated when written. Evolution complete."
When not to use it
- →If `.memory/wiki/specs/ideation/ideation-index.md` does not exist
- →When a full `/ideate` interview is required for free-form input
- →When the user has not approved the written content
Prerequisites
Limitations
- →Requires `.memory/wiki/specs/ideation/ideation-index.md` to exist
- →Does not perform a full `/ideate` interview for free-form input
- →Requires user approval before proceeding to cascade scope determination
How it compares
This skill provides a structured workflow for classifying and documenting new features and their cascading impacts, unlike a manual process that might miss dependencies or misplace documentation.
Compared to similar skills
evolve-feature-classify side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| evolve-feature-classify (this skill) | 0 | 3mo | No flags | Intermediate |
| create-plan | 36 | 8mo | Review | Beginner |
| project-planner | 32 | 9mo | Review | Intermediate |
| system-design | 19 | 9mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by RepairYourTech
View all by RepairYourTech →You might also like
create-plan
antinomyhq
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
system-design
lagz0ne
Use when designing, architecting, or planning a new system from requirements or ideas - transforms concepts into navigable design catalog using EventStorming methodology, Mermaid diagrams, and progressive elaboration through 5 phases (Requirements, Big Picture, Processes, Data/Flows, Integration)
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
sparc-methodology
ruvnet
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
spec-workflow
TencentCloudBase
Standard software engineering workflow for requirement analysis, technical design, and task planning. Use this skill when developing new features, complex architecture designs, multi-module integrations, or projects involving database/UI design.