- Use full model names (claude-haiku-4-5, etc.) in create-capability
- Add allowed-tools to gitea skill for tea/jq commands
- Set default model to opus in settings
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- tea issues output has title on line 2, not line 1
- Update sed command to extract from correct line
- Fixes branches being named "issue-N-" or "issue-N-untitled"
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Creates new user-invocable skill for fixing PRs based on review feedback:
- Takes multiple PR numbers as arguments
- Creates isolated fix worktrees for each PR
- Spawns pr-fixer agents in parallel
- Event-driven result handling
- Addresses review comments autonomously
- Commits and pushes fixes to Gitea using tea
- Shows detailed summary of all fixes
Uses tea and gitea skill (not gh). Pattern matches spawn-issues and
spawn-pr-reviews: Haiku orchestrator with allowed-tools.
Completes the spawn trilogy:
- spawn-issues: full workflow (implement → review → fix)
- spawn-pr-reviews: review only (read-only)
- spawn-pr-fixers: fix only (based on feedback)
Co-Authored-By: Claude Code <noreply@anthropic.com>
Creates new user-invocable skill for reviewing PRs:
- Takes multiple PR numbers as arguments
- Creates isolated review worktrees for each PR
- Spawns code-reviewer agents in parallel
- Event-driven result handling
- Posts review comments to Gitea using tea
- Read-only operation (no auto-fixes)
Uses tea and gitea skill (not gh), avoiding conflicts with base
system instructions.
Pattern matches spawn-issues: Haiku orchestrator with allowed-tools
for bash execution.
Co-Authored-By: Claude Code <noreply@anthropic.com>
The spawn-issues skill was missing the allowed-tools field that was present
in the old version. Without this field, the skill cannot execute bash commands,
causing permission errors when trying to create worktrees or call scripts.
Added: allowed-tools: Bash, Task, Read, TaskOutput
Co-Authored-By: Claude Code <noreply@anthropic.com>
Users were confused by ./scripts/ references, thinking they needed to copy
scripts into their project. Scripts are in ~/.claude/skills/worktrees/scripts/
and should be referenced with full paths.
Changes:
- Updated spawn-issues to use full script paths
- Updated worktrees skill with full paths in all examples
- Fixed gitea model name to claude-haiku-4-5
- Added tools list to issue-worker agent
Co-Authored-By: Claude Code <noreply@anthropic.com>
Restructure steps 7-8 to be clearer and more efficient:
- Merged "Assign Issues" and "Apply Labels" into single step
- Explicit nested loop structure: milestone → issues in that milestone
- Process one milestone at a time
- Combine milestone assignment + labels in single tea command
- Added clear examples
- Prevents confusion about looping and when to move on
Before: Separate loops for milestone assignment and label application
After: Single pass through milestones, process all issues per milestone
Co-Authored-By: Claude Code <noreply@anthropic.com>
Clarify that after user approves issues at decision gate, workflow should
automatically proceed to create all issues in Gitea without waiting for
another prompt.
Changes:
- Step 13: Clear yes/no question "Ready to create these issues in Gitea?"
- Step 14: Marked as "automatic after approval"
- Guidelines: Added "Automatic execution after approval" section with example
Prevents workflow from stopping and requiring user to explicitly request
issue creation after already approving the backlog.
Co-Authored-By: Claude Code <noreply@anthropic.com>
Add capability for organizing backlog into shippable business capabilities
using value-based milestones (not time-based phases).
Components:
- milestone-planning skill: Value-based framework, vertical slice test, one active milestone
- create-milestones skill: Orchestrator (Haiku) for analyzing and grouping issues
- milestone-planner agent: Groups issues into capabilities autonomously (Haiku)
Core Principles:
- Milestone = shippable business capability (not phase)
- One active milestone at a time (preserves focus)
- 5-25 issues per milestone (right-sized)
- Value labels: value/high, value/medium, value/low
- Risk labels: risk/high (optional)
- Vertical slice test (can be demoed independently)
- No dates (capability-based, not time-based)
Workflow: /create-milestones reads existing Gitea issues → analyzes capability
boundaries → groups into milestones → creates in Gitea → assigns issues →
applies labels → user manually activates ONE milestone
Co-Authored-By: Claude Code <noreply@anthropic.com>
Split gitea skill into main file and reference documentation.
Main SKILL.md now focuses on core commands (154 lines, down from 201),
with setup/auth and CI/Actions moved to reference files.
Co-Authored-By: Claude Code <noreply@anthropic.com>
Claude Code has unified commands into skills with the user-invocable
frontmatter field. This migration:
- Converts 20 commands to skills with user-invocable: true
- Consolidates docs into single writing-capabilities.md
- Rewrites capability-writing skill for unified model
- Updates CLAUDE.md, Makefile, and other references
- Removes commands/ directory
Skills now have two types:
- user-invocable: true - workflows users trigger with /name
- user-invocable: false - background knowledge auto-loaded
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Set explicit model preferences to optimize for speed vs capability:
- haiku: 11 commands, 2 agents (issue-worker, pr-fixer), 10 skills
Fast execution for straightforward tasks
- sonnet: 4 commands (groom, improve, plan-issues, review-pr),
1 agent (code-reviewer)
Better judgment for analysis and review tasks
- opus: 2 commands (arch-refine-issue, arch-review-repo),
1 agent (software-architect)
Deep reasoning for architectural analysis
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The planning process previously jumped directly from understanding a feature
to breaking it down into issues. This led to proposing issues without first
understanding the user's actual workflow and where the gaps are.
Added a discovery phase that requires walking through:
- Who is the specific user
- What is their goal
- Step-by-step workflow to reach the goal
- What exists today
- Where the workflow breaks or has gaps
- What's the MVP
Issues are now derived from workflow gaps rather than guessing.
Closes#29
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Creates a skill that teaches how to design and create capabilities
(skill + command + agent combinations) for the architecture repository.
Includes:
- Component templates for skills, commands, and agents
- Decision tree and matrix for when to use each component
- Model selection guidance (haiku/sonnet/opus)
- Naming conventions and anti-patterns to avoid
- References to detailed documentation in docs/
- Checklists for creating each component type
Closes#74
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add Architecture Beliefs section to manifesto with outcome-focused beliefs:
auditability, business language in code, independent evolution, explicit over implicit
- Create software-architecture.md as human-readable documentation
- Enhance software-architecture skill with beliefs→patterns mapping (DDD, Event
Sourcing, event-driven communication) and auto-trigger description
- Update work-issue command to reference skill and check project architecture
- Update issue-worker agent with software-architecture skill
- Add Architecture section template to vision-management skill
The skill is now auto-triggered when implementing, reviewing, or planning
architectural work. Project-level architecture choices go in vision.md.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Creates the foundational skill that encodes software architecture
best practices, review checklists, and patterns for Go and generic
architecture guidance.
Closes#56
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Adds guidance to prefer vertical slices (user-visible value) over
horizontal slices (technical layers) when planning and writing issues.
roadmap-planning skill:
- New "Vertical vs Horizontal Slices" section
- Demo test: "Can a user demo/test this independently?"
- Good vs bad examples table
- When horizontal slices are acceptable
issue-writing skill:
- New "Vertical Slices" section
- Demo test guidance
- Good vs bad issue titles table
- User-focused issue framing examples
Closes#31
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Skills are knowledge modules referenced by commands, not
directly invoked by users. Added user-invocable: false to:
- backlog-grooming (used by /groom)
- claude-md-writing (used by /update-claude-md)
- code-review (used by /review-pr)
- issue-writing (used by /create-issue)
- roadmap-planning (used by /plan-issues)
- vision-management (used by /vision, /manifesto)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Create claude-md-writing skill with best practices for CLAUDE.md files
- Create repos.md registry of all repos with status (Active/Planned/Splitting)
- Update /create-repo to include organization context section
- Update repo-conventions to reference new skill
Each repo's CLAUDE.md now links to manifesto, repos.md, and vision.md
so Claude always understands the bigger picture.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Skill documents standard repo structure, naming conventions,
open vs proprietary guidance, and CI/CD patterns.
Command scaffolds new repos with vision.md, CLAUDE.md, Makefile,
CI workflow, and .gitignore - all linked to the architecture repo.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Product repos find the manifesto at ../architecture/manifesto.md.
This allows the architecture repo to be a sibling of product repos.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Rebuild vision.md to trace personas, jobs, and principles back to manifesto
- Improve /vision command with inheritance guidance and templates
- Update vision-management skill with explicit inheritance rules and formats
Product visions now explicitly extend (not duplicate) organization manifesto.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Restructured skill to clearly distinguish:
- Manifesto: Organization-level (architecture repo)
- Vision: Product-level (product repos)
Key additions:
- Architecture table showing all three levels with commands
- Manifesto section with structure, when to update, creation steps
- Vision section clarified as product-level extending manifesto
- Relationship diagram showing inheritance model
- Example of persona inheritance (org → product)
- Continuous improvement loop including retro → encoding flow
- Quick reference table for common questions
Closes#43🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The vision system now guides defining WHO we build for and WHAT they're
trying to achieve before jumping into goals and issues.
Updated vision-management skill:
- New vision.md structure with Personas and Jobs to Be Done sections
- Guidance for defining good personas (specific, characterized, limited)
- Guidance for jobs to be done (outcome-focused, in their voice, pain-aware)
- Milestones now tied to personas and jobs with structured descriptions
- Issue alignment checks persona/job fit before milestone fit
Updated vision command:
- Guides through persona and JTBD definition when creating vision
- Output format shows personas and jobs prominently
- Guidelines emphasize traceability to personas
Updated plan-issues command:
- Identifies persona and job before breaking down work
- Plan presentation includes For/Job/Supports context
- Flags misalignment with persona/job, not just goals
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Updated skills and commands to identify and formally link issue
dependencies using tea CLI:
Skills updated:
- issue-writing: Document deps in description + link with tea CLI
- backlog-grooming: Check for formal dependency links in checklist
- roadmap-planning: Link dependencies after creating issues
Commands updated:
- create-issue: Ask about and link dependencies for new issues
- plan-issues: Create in dependency order, link with tea issues deps add
- groom: Check dependency status, suggest missing links
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Refactored the vision system to separate concerns:
- vision.md remains the stable "north star" philosophy document
- Gitea milestones now track goals with automatic progress via issue counts
- Updated /vision, /retro, and /create-issue commands to auto-assign milestones
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Transforms the product-manager from a reactive backlog manager into a
vision-driven system with continuous improvement capabilities.
New components:
- vision-management skill: How to create, maintain, and evolve product vision
- /vision command: View, create, or update product vision (syncs to Gitea)
- /improve command: Identify gaps between vision goals and backlog
Enhanced existing components:
- product-manager agent: Now vision-aware with strategic prioritization
- /retro command: Connects learnings back to vision updates
- /plan-issues command: Shows vision alignment for planned work
The vision lives in two places: vision.md (source of truth) and a Gitea
issue labeled "vision" for integration with the issue workflow.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The tea CLI doesn't have a command to output PR diff content directly.
The -f diff flag only returns a URL. Updated docs to use tea pulls
checkout followed by git diff main...HEAD.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Updated all skill descriptions with proper trigger terms following
the pattern: "What it does. Use when [trigger terms]."
Skills updated:
- code-review: triggers on PR review, code quality, bugs, security
- issue-writing: triggers on creating issues, bug reports, features
- backlog-grooming: triggers on grooming, reviewing issue quality
- roadmap-planning: triggers on planning features, breaking down work
Updated docs/writing-skills.md:
- Added YAML frontmatter requirements section
- Documented required and optional fields
- Added guidance on writing effective descriptions
- Updated "How Skills are Loaded" to reflect model-invoked behavior
- Added note about subagent skill access
- Updated checklist with frontmatter requirements
- Added reference to official documentation
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The description now follows the documented pattern:
1. What it does: specific actions (view, create, manage)
2. When to use: trigger terms users would mention (issues, PRs, tea, gitea)
This helps Claude know when to automatically apply the skill.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The allowed-tools field in skills RESTRICTS which tools can be used,
not grants permission. The tea CLI permissions are already configured
in settings.json via permissions.allow.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
When the gitea skill is active, Claude can now use tea CLI commands
without asking permission. This enables smoother workflow when using
commands like /work-issue that rely on the gitea skill.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Skills require YAML frontmatter with name and description fields
for Claude Code to automatically discover and load them. Added
frontmatter to all five skill files:
- gitea: CLI for issues, PRs, and repository management
- code-review: Guidelines for reviewing code changes
- issue-writing: How to write clear, actionable issues
- backlog-grooming: Review and improve existing issues
- roadmap-planning: Plan features and create issues
Closes#12🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Heredoc syntax causes tea comment to be backgrounded and fail silently.
Updated Comments section to:
- Use quoted strings with literal newlines for multiline comments
- Add warning about avoiding heredoc syntax
Closes#10🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Documents that tea CLI uses --description/-d flag for PR body content,
not --body like the gh CLI. This helps avoid failed commands when
transitioning from gh CLI.
Closes#5🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add Comments section to gitea skill with examples
- Update code-reviewer agent with explicit tea CLI commands
for posting comments, approving, and merging PRs
Closes#6🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The tea CLI doesn't have a `view` subcommand - use `tea issues <number>`
directly instead of `tea issues view <number>`.
- Fix example in ARCHITECTURE.md
- Add clarifying tip in gitea skill to prevent this common mistake
Closes#2🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Replace fj CLI with tea CLI across all commands
- Create new gitea skill, remove forgejo skill
- Update all agents to use gitea skill
- Update commands to use skill-based approach (reference skills instead of embedding CLI commands)
- Update all documentation (README, ARCHITECTURE, VISION, writing guides)
- Swap git remotes: origin now points to git.flowmade.one (Gitea)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
