flowmade-one/architecture
3
0
Fork 0
Code Issues 15 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Create /create-capability command for scaffolding capability sets #75

New Issue
Closed
opened 2026-01-10 14:27:31 +00:00 by HugoNijhuis · 0 comments
HugoNijhuis commented 2026-01-10 14:27:31 +00:00
Owner
Copy Link

Summary

Create a command that helps users create new capabilities for this repository. A capability may be a single component or a cohesive set (skill + command + agent).

For

Flowmade Developers - "Help me encode best practices so AI applies them"

Command Workflow

/create-capability <description>

  1. Understand the capability: Analyze user's description to understand what they want to build

  2. Determine components needed: Based on the description, recommend which components:

    • Skill only (knowledge to apply automatically)
    • Command only (workflow using existing skills)
    • Command + Skill (new knowledge + workflow)
    • Command + Agent (workflow with isolated worker)
    • Full set: Skill + Command + Agent

  3. Gather information:

    • Name for the capability
    • Description/purpose
    • For each component: specific details

  4. Select appropriate models:

    • Commands: haiku for simple, sonnet for most
    • Agents: sonnet for most, opus for deep reasoning

  5. Generate files from templates:

    • Use capability-writing skill for templates
    • Ensure proper references between components:
      • Command references skill via @~/.claude/skills/name/SKILL.md
      • Agent lists skill in skills: frontmatter
      • Command spawns agent via Task tool if needed

  6. Present for approval: Show generated files before creating

  7. Create files in correct locations:

    • skills/name/SKILL.md
    • commands/name.md
    • agents/name/AGENT.md

Example Usage

User: /create-capability I want to add support for reviewing database migrations

Claude: Based on your description, I recommend creating:
- **Skill**: `migration-review` - Knowledge about what makes a good migration
- **Command**: `/review-migration` - Entry point for users
- **Agent**: `migration-reviewer` - Isolated analysis (optional, if complex)

Let me gather some details...

Acceptance Criteria

  • Command created at commands/create-capability.md
  • References capability-writing skill
  • Determines appropriate component set based on description
  • Generates cohesive files with proper inter-references
  • Selects appropriate models for each component
  • Shows preview before creating files
  • Creates files in correct locations

Dependencies

  • #74 (capability-writing skill)

Context

Part of meta-tooling for extending the architecture repo. Makes it easy to add new capabilities following established patterns.

## Summary Create a command that helps users create new capabilities for this repository. A capability may be a single component or a cohesive set (skill + command + agent). ## For Flowmade Developers - "Help me encode best practices so AI applies them" ## Command Workflow ``` /create-capability <description> ``` 1. **Understand the capability**: Analyze user's description to understand what they want to build 2. **Determine components needed**: Based on the description, recommend which components: - Skill only (knowledge to apply automatically) - Command only (workflow using existing skills) - Command + Skill (new knowledge + workflow) - Command + Agent (workflow with isolated worker) - Full set: Skill + Command + Agent 3. **Gather information**: - Name for the capability - Description/purpose - For each component: specific details 4. **Select appropriate models**: - Commands: haiku for simple, sonnet for most - Agents: sonnet for most, opus for deep reasoning 5. **Generate files from templates**: - Use capability-writing skill for templates - Ensure proper references between components: - Command references skill via `@~/.claude/skills/name/SKILL.md` - Agent lists skill in `skills:` frontmatter - Command spawns agent via Task tool if needed 6. **Present for approval**: Show generated files before creating 7. **Create files** in correct locations: - `skills/name/SKILL.md` - `commands/name.md` - `agents/name/AGENT.md` ## Example Usage ``` User: /create-capability I want to add support for reviewing database migrations Claude: Based on your description, I recommend creating: - **Skill**: `migration-review` - Knowledge about what makes a good migration - **Command**: `/review-migration` - Entry point for users - **Agent**: `migration-reviewer` - Isolated analysis (optional, if complex) Let me gather some details... ``` ## Acceptance Criteria - [ ] Command created at `commands/create-capability.md` - [ ] References capability-writing skill - [ ] Determines appropriate component set based on description - [ ] Generates cohesive files with proper inter-references - [ ] Selects appropriate models for each component - [ ] Shows preview before creating files - [ ] Creates files in correct locations ## Dependencies - #74 (capability-writing skill) ## Context Part of meta-tooling for extending the architecture repo. Makes it easy to add new capabilities following established patterns.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
HugoNijhuis fluxcd-bot renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#76 Add validation and interactive guidance to /create-capability
flowmade-one/architecture
Depends on
#74 Create capability-writing skill with templates and design guidance
flowmade-one/architecture
Reference: flowmade-one/architecture#75
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?