Update documentation and apply new frontmatter capabilities: Documentation: - Add user-invocable, context, agent, hooks fields to writing-skills.md - Add disallowedTools, permissionMode, hooks fields to writing-agents.md - Add model, context, hooks, allowed-tools fields to writing-commands.md - Document skill hot-reload, built-in agents, background execution Skills: - Add user-invocable: false to gitea (CLI reference) - Add user-invocable: false to repo-conventions (standards reference) Commands: - Add context: fork to heavy exploration commands (improve, plan-issues, create-repo, update-claude-md) - Add missing argument-hint to roadmap, manifesto, improve Agents: - Add disallowedTools: [Edit, Write] to code-reviewer for safety Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1.8 KiB
description, argument-hint, context
| description | argument-hint | context |
|---|---|---|
| Plan and create issues for a feature or improvement. Breaks down work into well-structured issues with vision alignment. | <feature-description> | fork |
Plan Feature: $1
@/.claude/skills/gitea/SKILL.md
@/.claude/skills/roadmap-planning/SKILL.md
@/.claude/skills/issue-writing/SKILL.md
@/.claude/skills/vision-management/SKILL.md
-
Check vision context: If
vision.mdexists, read it to understand personas, jobs to be done, and goals -
Identify persona: Which persona does "$1" serve?
-
Identify job: Which job to be done does this enable?
-
Understand the feature: Analyze what "$1" involves
-
Explore the codebase if needed to understand context
-
Break down into discrete, actionable issues:
- Each issue should be independently completable
- Clear dependencies between issues
- Appropriate scope (not too big, not too small)
-
Present the plan (include vision alignment if vision exists):
## Proposed Issues for: $1 For: [Persona name] Job: "[Job to be done this enables]" Supports: [Milestone/Goal name] 1. [Title] - Brief description Dependencies: none 2. [Title] - Brief description Dependencies: #1 3. [Title] - Brief description Dependencies: #1, #2If the feature doesn't align with any persona/job/goal, note this and ask if:
- A new persona or job should be added to the vision
- A new milestone should be created
- This should be added as a non-goal
- Proceed anyway (with justification)
-
Ask for approval before creating issues
-
Create issues in dependency order (blockers first)
-
Link dependencies using
tea issues deps add <issue> <blocker>for each dependency -
Present summary with links to created issues and dependency graph