skills.rest
ChazzCoin
ChazzCoinCOMMUNITY
Explore all skills by this author →
GitHub

feature

Automate feature plan authoring and notice refreshing across multiple sub-repositories.

Updated May 7, 2026
Search Tags:#feature planning#project visibility#feature management#software orchestration#cross-repo coordination
One-click install
npx skills add https://github.com/ChazzCoin/claude-orchestrator --skill feature-chazzcoin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/ChazzCoin/claude-orchestrator/tree/main/kit/skills/feature
Command: npx skills add https://github.com/ChazzCoin/claude-orchestrator --skill feature-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables the authoring of cross-cutting feature plans that span multiple sub-repositories, providing visibility and coordination for feature implementation across the software stack.

Core Features & Use Cases

  • Feature Plan Creation: Author new feature plans and track them over time.
  • Sub-repo Coordination: Automatically generate notices for each affected sub-repository, ensuring alignment across the team.
  • Migration Linking: Identify and link migrations that need to be executed as part of the feature plan.
  • Mode Selection: Use "Open" mode to create new features or "Refresh" mode to update existing notices after changes.
  • **Quick Start Start a new feature planning session with "/feature", or refresh existing notices with "/feature refresh".

Use the feature skill to plan a new cross-cutting feature.

Frequently Asked Questions about feature

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

FAQPage Schema
How do I coordinate feature planning across multiple repositories?▼

Cross-repo feature planning requires orchestrating feature plans and generating notices for each affected sub-repository to ensure team alignment and visibility. You provide feature scope and coordination details, and the system renders notice files for each repo.

What is the best way to maintain project visibility for cross-cutting software features?▼

Maintaining project visibility involves authoring feature plans that span multiple sub-repositories and automatically generating coordination notices to track implementation across the software stack over time.

How do I update existing feature notices after changes to a multi-repo feature plan?▼

To update existing feature notices, use the "Refresh" mode by running the refresh command. This re-renders orchestrator-side template notices across all affected sub-repositories to reflect recent changes.

Can I link migrations to a cross-cutting feature plan?▼

Yes, feature plan creation supports migration linking. You can identify and link migrations that need to be executed as part of the overall feature plan across the affected sub-repositories.

Do I need to manually create notice files for each sub-repo in a feature plan?▼

No, notice files are generated automatically through orchestrator-side template rendering. You provide the feature scope and coordination details, and the system outputs the necessary notices for each affected sub-repository.

Related Skills

Explore More Product & Management Skills→
Soul-Brews-StudioSoul-Brews-Studio
116

morpheus

Analyze code repositories to generate structured, testable speculations with traceable reasoning.

Official
Advanced
xpgcrxxpgcrx
5

steering

Create steering files and tasklists to track work through planning, implementation, and review phases.

Community
Advanced
nnexainnexai
1

gsd-check-todos

List and filter pending development tasks with roadmap correlation.

Community
Intermediate
bettercallzaalbettercallzaal
1

fishbowlz

Sync ZAO OS changes to GitHub and deploy to fishbowlz.com.

Community
Intermediate