Skip to content

fix: add user-invocable: false to all DevFlow skills#42

Merged
dean0x merged 3 commits intomainfrom
fix/skills-frontmatter-alignment
Jan 26, 2026
Merged

fix: add user-invocable: false to all DevFlow skills#42
dean0x merged 3 commits intomainfrom
fix/skills-frontmatter-alignment

Conversation

@dean0x
Copy link
Copy Markdown
Owner

@dean0x dean0x commented Jan 26, 2026

Summary

  • Add user-invocable: false to all 25 DevFlow skills to hide them from the / autocomplete menu
  • Simplify README to focus on commands (user-facing) rather than implementation details (agents, skills architecture)

Changes

Skills Frontmatter (25 files)

All skills now have user-invocable: false so they don't appear in the slash command menu but can still auto-activate based on context.

README

Reduced from 510 to 167 lines by removing:

  • Skills architecture (tiers, iron laws, how skills work)
  • Agent details (orchestration patterns, spawning)
  • Internal implementation details

Focused on what users need: commands, workflows, installation.

Test Plan

  • Run devflow init to reinstall skills
  • Verify no DevFlow skills appear in / autocomplete
  • Verify commands (/specify, /implement, etc.) still work
  • Verify skills still auto-activate during implementation

Closes #41

Dean Sharon added 3 commits January 26, 2026 14:25
- Add user-invocable: false to 18 Foundation/Pattern skills (Tier 1/1b)
  to prevent them from appearing in / autocomplete menu
- Add disable-model-invocation: true to commit and pull-request skills
  to prevent automatic invocation without explicit user intent

Closes #41
- Replace disable-model-invocation with user-invocable: false on commit
  and pull-request skills (agent should auto-activate these)
- Add user-invocable: false to remaining Tier 2/3 skills (code-smell,
  input-validation, test-design, typescript, react)

All 25 DevFlow skills now hidden from / menu but can still auto-activate.
Remove internal details (agents, skills architecture, tiers, iron laws)
that are implementation details users don't need to know about.

Focus on:
- What commands are available
- What each command does
- How to use them in a workflow
- Installation and CLI options
@dean0x dean0x merged commit b318277 into main Jan 26, 2026
@dean0x dean0x deleted the fix/skills-frontmatter-alignment branch January 26, 2026 12:58
dean0x added a commit that referenced this pull request Mar 9, 2026
## Summary

- Moves branch name derivation into the Git agent's `setup-task`
operation, so `/implement #42` automatically creates
`feature/42-add-jwt-auth` instead of `task-2025-01-15_1430`
- Issue input derives `{type}/{number}-{slug}` from labels and title
(bug→fix, docs→docs, refactor→refactor, default→feature)
- Free-text input infers type from keywords and slugifies as
`{type}/{slug}`
- Falls back to `task-{YYYY-MM-DD_HHMM}` when neither issue nor
description is provided
- Removes `TASK_ID` generation from both `implement.md` and
`implement-teams.md` — the Git agent now owns and returns the branch
name

## Test plan

- [ ] Run `npm run build` — verify clean build with agent distributed to
plugins
- [ ] `/implement #<issue-with-bug-label>` — verify branch:
`fix/{number}-{slug}`
- [ ] `/implement #<issue-no-labels>` — verify branch:
`feature/{number}-{slug}`
- [ ] `/implement add JWT auth` — verify branch: `feature/add-jwt-auth`
- [ ] `/implement fix login bug` — verify branch: `fix/login-bug`
- [ ] `/implement` (conversation context only) — verify fallback:
`task-{timestamp}`

Co-authored-by: Dean Sharon <deanshrn@gmain.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix: Add missing frontmatter fields to DevFlow skills

1 participant