Update the feature workflow commands to create GitHub issues per phase
instead of per individual task. This reduces issue clutter while still
maintaining granular task tracking via checklists within phase issues.
Key changes:
**publish-to-github.md:**
- Create phase issues instead of individual task issues
- Each phase issue contains the full task checklist from implementation plan
- Add support for `[complex]` marker to break out complex tasks as separate issues
- Update Epic to link to phase issues instead of tasks
- Update github.md template to show phases and optional complex task issues
**create-feature.md:**
- Add documentation for `[complex]` task marker
- Update implementation plan format example with nested sub-tasks
- Add "When to Use [complex]" guidance section
**continue-feature.md:**
- Rewrite workflow to work with phase issues instead of task issues
- Add logic to identify current phase and find unchecked tasks
- Support both phase issue tasks and complex task issues
- Add step to update phase issue checklist after completing tasks
- Update completion reporting for phase-based progress
- Renumber steps (8.x → 7.x) for consistency
**Hybrid approach:**
- Default: one issue per phase with task checklists
- Optional: break out tasks marked `[complex]` or with nested sub-tasks
- Complex task issues link back to parent phase issue
This change results in ~5 issues (1 epic + 4 phases) instead of ~47 issues
for a typical feature, significantly reducing GitHub issue noise.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Extends the /create-feature command to generate a third file that
extracts manual/human tasks into a dedicated checklist for better
visibility.
Changes:
- Add step 4 to create action-required.md with manual tasks
- Add template format with Before/During/After Implementation sections
- Add "no manual steps" template variant
- Update Next Steps to prioritize reviewing action-required.md
- Add note listing common manual task types (API keys, env vars, etc.)
- Bump create-agentic-app version to 1.1.27
Manual tasks (like account creation, environment variables, OAuth setup)
are now surfaced in a separate file so they're harder to miss during
feature implementation.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
This commit introduces a comprehensive feature management workflow that
integrates with GitHub Issues and Projects for better task tracking and
team collaboration.
## New Commands Added
- `/publish-to-github`: Publishes features from /specs to GitHub by:
- Creating an Epic issue with full requirements
- Creating individual task issues for each implementation step
- Setting up a GitHub Project board linked to the repository
- Creating labels for organization (epic, feature/*, phase-*)
- Generating a github.md reference file in the specs folder
- `/continue-feature`: Implements the next available task by:
- Querying open issues for the feature
- Checking task dependencies to find unblocked work
- Updating GitHub Project board status (In Progress -> Done)
- Adding implementation details as issue comments
- Providing fallback to implementation-plan.md when offline
## Updated Commands
- `/create-feature`: Enhanced with clearer structure including:
- Detailed implementation plan format template
- Requirements for atomic, agent-implementable tasks
- Guidance on next steps after feature creation
- Better documentation for the /specs folder structure
## Package Updates
- Bumped version from 1.1.24 to 1.1.25
All changes are mirrored in both the root .claude/commands/ folder
and the create-agentic-app/template/.claude/commands/ folder to ensure
new projects created with the CLI have access to these workflows.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Remove platform-specific Windows path from additionalDirectories in Claude settings files to ensure cross-platform compatibility across Windows, macOS, and Linux.
Renamed the ui-developer agent to ui-expert for better clarity and
consistency with naming conventions. This change affects both the root
project and the create-agentic-app template.
Changes made:
- Renamed .claude/agents/ui-developer.md to ui-expert.md in both root and template
- Updated agent name and references within agent configuration
- Bumped create-agentic-app version from 1.1.14 to 1.1.15
- Updated corresponding package-lock.json with new version
The agent's functionality and responsibilities remain unchanged - this is
purely a naming improvement to better reflect its role as a UI expert
rather than just a developer.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
