From 9332df22537b161db314649ab795dfc10d044a87 Mon Sep 17 00:00:00 2001 From: Leon van Zyl Date: Wed, 3 Dec 2025 12:23:07 +0200 Subject: [PATCH] feat: add action-required.md to /create-feature command MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- .claude/commands/create-feature.md | 56 +++++++++++++++++-- create-agentic-app/package-lock.json | 4 +- create-agentic-app/package.json | 2 +- .../.claude/commands/create-feature.md | 56 +++++++++++++++++-- 4 files changed, 107 insertions(+), 11 deletions(-) diff --git a/.claude/commands/create-feature.md b/.claude/commands/create-feature.md index af5eb71..47a1127 100644 --- a/.claude/commands/create-feature.md +++ b/.claude/commands/create-feature.md @@ -26,7 +26,14 @@ This command creates a new feature specification folder with requirements and im - Tasks should be specific enough for an agent to implement independently - Include dependencies between tasks where relevant -4. **Exclude testing tasks** +4. **Create action-required.md** + - Extract all manual steps that require human action + - Include tasks like: account creation, API key setup, environment variables, third-party service configuration, DNS settings, etc. + - Each task has a checkbox and brief context (one-liner explaining why it's needed) + - Keep these tasks in the implementation plan as well (for full context) + - If no manual steps exist, create the file with a "None required" note + +5. **Exclude testing tasks** - Do NOT include unit or e2e testing tasks - UNLESS the user explicitly asks for testing to be included @@ -36,6 +43,7 @@ Ask the user what the requirements are first, then create the spec subfolder wit - `requirements.md` - `implementation-plan.md` +- `action-required.md` ## Implementation Plan Format @@ -69,6 +77,44 @@ Brief summary of what will be built. ... ``` +## action-required.md Format + +Use this structure for `action-required.md`: + +```markdown +# Action Required: {Feature Name} + +Manual steps that must be completed by a human. These cannot be automated. + +## Before Implementation + +- [ ] **{Action}** - {Brief reason why this is needed} + +## During Implementation + +- [ ] **{Action}** - {Brief reason} + +## After Implementation + +- [ ] **{Action}** - {Brief reason} + +--- + +> **Note:** These tasks are also listed in context within `implementation-plan.md` +``` + +### When No Manual Steps Exist + +If the feature has no manual steps, create the file with: + +```markdown +# Action Required: {Feature Name} + +No manual steps required for this feature. + +All tasks can be implemented automatically. +``` + ## Next Steps After creating the feature, inform the user: @@ -77,9 +123,10 @@ After creating the feature, inform the user: > > **Next steps:** > -> 1. Review the requirements and implementation plan -> 2. Run `/publish-to-github` to create GitHub issues and project -> 3. Use `/continue-feature` or drag the folder into a conversation to start implementing +> 1. Review `action-required.md` for tasks you need to complete manually +> 2. Review the requirements and implementation plan +> 3. Run `/publish-to-github` to create GitHub issues and project +> 4. Use `/continue-feature` to start implementing ## Notes @@ -87,3 +134,4 @@ After creating the feature, inform the user: - Tasks should produce working, testable code when complete - Use clear, descriptive task names that explain what will be done - Note dependencies explicitly when tasks must be done in order +- Common manual tasks: account creation, API key generation, environment variables, OAuth app configuration, DNS/domain setup, billing setup, third-party service registration diff --git a/create-agentic-app/package-lock.json b/create-agentic-app/package-lock.json index 78071d0..7b04d68 100644 --- a/create-agentic-app/package-lock.json +++ b/create-agentic-app/package-lock.json @@ -1,12 +1,12 @@ { "name": "create-agentic-app", - "version": "1.1.26", + "version": "1.1.27", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "create-agentic-app", - "version": "1.1.26", + "version": "1.1.27", "license": "MIT", "dependencies": { "chalk": "^5.3.0", diff --git a/create-agentic-app/package.json b/create-agentic-app/package.json index 99f142d..b5d1bb0 100644 --- a/create-agentic-app/package.json +++ b/create-agentic-app/package.json @@ -1,6 +1,6 @@ { "name": "create-agentic-app", - "version": "1.1.26", + "version": "1.1.27", "description": "Scaffold a new agentic AI application with Next.js, Better Auth, and AI SDK", "type": "module", "bin": { diff --git a/create-agentic-app/template/.claude/commands/create-feature.md b/create-agentic-app/template/.claude/commands/create-feature.md index af5eb71..47a1127 100644 --- a/create-agentic-app/template/.claude/commands/create-feature.md +++ b/create-agentic-app/template/.claude/commands/create-feature.md @@ -26,7 +26,14 @@ This command creates a new feature specification folder with requirements and im - Tasks should be specific enough for an agent to implement independently - Include dependencies between tasks where relevant -4. **Exclude testing tasks** +4. **Create action-required.md** + - Extract all manual steps that require human action + - Include tasks like: account creation, API key setup, environment variables, third-party service configuration, DNS settings, etc. + - Each task has a checkbox and brief context (one-liner explaining why it's needed) + - Keep these tasks in the implementation plan as well (for full context) + - If no manual steps exist, create the file with a "None required" note + +5. **Exclude testing tasks** - Do NOT include unit or e2e testing tasks - UNLESS the user explicitly asks for testing to be included @@ -36,6 +43,7 @@ Ask the user what the requirements are first, then create the spec subfolder wit - `requirements.md` - `implementation-plan.md` +- `action-required.md` ## Implementation Plan Format @@ -69,6 +77,44 @@ Brief summary of what will be built. ... ``` +## action-required.md Format + +Use this structure for `action-required.md`: + +```markdown +# Action Required: {Feature Name} + +Manual steps that must be completed by a human. These cannot be automated. + +## Before Implementation + +- [ ] **{Action}** - {Brief reason why this is needed} + +## During Implementation + +- [ ] **{Action}** - {Brief reason} + +## After Implementation + +- [ ] **{Action}** - {Brief reason} + +--- + +> **Note:** These tasks are also listed in context within `implementation-plan.md` +``` + +### When No Manual Steps Exist + +If the feature has no manual steps, create the file with: + +```markdown +# Action Required: {Feature Name} + +No manual steps required for this feature. + +All tasks can be implemented automatically. +``` + ## Next Steps After creating the feature, inform the user: @@ -77,9 +123,10 @@ After creating the feature, inform the user: > > **Next steps:** > -> 1. Review the requirements and implementation plan -> 2. Run `/publish-to-github` to create GitHub issues and project -> 3. Use `/continue-feature` or drag the folder into a conversation to start implementing +> 1. Review `action-required.md` for tasks you need to complete manually +> 2. Review the requirements and implementation plan +> 3. Run `/publish-to-github` to create GitHub issues and project +> 4. Use `/continue-feature` to start implementing ## Notes @@ -87,3 +134,4 @@ After creating the feature, inform the user: - Tasks should produce working, testable code when complete - Use clear, descriptive task names that explain what will be done - Note dependencies explicitly when tasks must be done in order +- Common manual tasks: account creation, API key generation, environment variables, OAuth app configuration, DNS/domain setup, billing setup, third-party service registration