skills.rest
DavidsonGomes
DavidsonGomesCOMMUNITY
Explore all skills by this author →
GitHub

evo-set-feature

Set the active feature context and create planning and implementation artifact subfolders.

Updated Apr 6, 2026
Search Tags:#feature-context#artifact-management#config.yaml#set-feature#planning_artifacts#implementation_artifacts
One-click install
npx skills add https://github.com/DavidsonGomes/claude_cowork_workspace --skill evo-set-feature
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: evo-set-feature
Source: https://github.com/DavidsonGomes/claude_cowork_workspace/tree/main/.claude/skills/evo-set-feature
Command: npx skills add https://github.com/DavidsonGomes/claude_cowork_workspace --skill evo-set-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sets or switches the active feature context to organize artifacts by feature, ensuring consistent naming and storage.

Core Features & Use Cases

  • Creates and maintains a per-feature namespace for planning_artifacts and implementation_artifacts.
  • Updates the configuration to reflect the currently active feature so all future artifacts are correctly scoped.
  • Validates a feature slug and auto-creates the required subfolders if missing.

Quick Start

Set the active feature by providing a short kebab-case slug when prompted.

Frequently Asked Questions about evo-set-feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize planning and implementation artifacts by feature in my project?▼

To organize artifacts by feature, you need to set or switch the active feature context. This creates dedicated planning_artifacts and implementation_artifacts subfolders for each feature, ensuring consistent naming and scoped storage.

How does setting an active feature update project configuration?▼

Setting an active feature updates the project configuration by modifying the active_feature field in the config.yaml file located at the project root. This ensures all future artifacts are correctly scoped to the current feature.

Do I need to manually create subfolders when switching to a new feature context?▼

No, you do not need to manually create subfolders. When you set the active feature using a kebab-case slug, the system auto-creates the required planning_artifacts and implementation_artifacts subfolders if they are missing.

What format should the feature slug follow when setting the active feature?▼

The feature slug should follow a short kebab-case format. This validates the feature name and updates the configuration to maintain a per-feature namespace for your artifacts.

What is the purpose of maintaining a per-feature namespace for project artifacts?▼

Maintaining a per-feature namespace isolates planning_artifacts and implementation_artifacts by feature. It solves the problem of artifact clutter by ensuring consistent naming and storage specific to each active feature context.

Related Skills

Explore More Product & Management Skills→
DavidsonGomesDavidsonGomes

evo-generate-project-context

Generate project-context.md by following the Evo workflow instructions.

Community
Advanced
WizarckWizarck

bmad-create-story

Generate a complete BMAD story file with sprint status and artifact references.

Community
Advanced
AlexHramovichAlexHramovich

agntcms-rename-slug

Rename page and draft slugs with atomic updates and conflict checks.

Community
Intermediate
brmatolabrmatola

plan-complete

Move completed plans from plans/active to plans/complete with git commits.

Community
Basic