mirror of
https://github.com/AyuGram/AyuGramDesktop.git
synced 2026-07-25 06:54:43 +00:00
John Preston
123 lines
3.2 KiB
Markdown
123 lines
3.2 KiB
Markdown
---
|
|
description: Plan and create a repetitive task automation (prompt.md + tasks.json pair)
|
|
allowed-tools: Read, Write, Edit, Glob, Grep, Bash(mkdir:*), Bash(ls:*), AskUserQuestion
|
|
---
|
|
|
|
# Task Planner - Create Automated Task Workflows
|
|
|
|
You are setting up a new **repetitive task automation** for Claude Code. The goal is to create a folder in `.ai/<featurename>/` containing:
|
|
- `prompt.md` - Detailed instructions for the autonomous agent
|
|
- `tasks.json` - List of tasks with completion tracking
|
|
|
|
This pair can then be executed via `.claude/iterate.ps1 <featurename>`.
|
|
|
|
## Your Workflow
|
|
|
|
### 1. Understand the Goal
|
|
|
|
First, understand what the user wants to automate. Ask clarifying questions using AskUserQuestion if needed:
|
|
- What is the overall goal/feature being implemented?
|
|
- What are the individual tasks involved?
|
|
- Are there dependencies between tasks?
|
|
- What files/areas of the codebase are involved?
|
|
- Are there any reference examples or patterns to follow?
|
|
|
|
### 2. Choose a Feature Name
|
|
|
|
The `<featurename>` should be:
|
|
- Short (1-2 words, lowercase, hyphen-separated)
|
|
- Easy to type on command line
|
|
- Descriptive of the work being done
|
|
- Not already used in `.ai/`
|
|
|
|
Check existing folders:
|
|
```bash
|
|
ls .ai/
|
|
```
|
|
|
|
Suggest a name to the user or let them specify one directly via $ARGUMENTS.
|
|
|
|
|
|
### 3. Create the Folder and Files
|
|
|
|
Create `.ai/<featurename>/`:
|
|
|
|
**prompt.md** should include:
|
|
- Overview of what we're doing
|
|
- Architecture/context needed
|
|
- Step-by-step instructions for each task type
|
|
- Code patterns and examples
|
|
- Build/test commands
|
|
- Commit message format (see below)
|
|
|
|
### Commit Message Guidelines
|
|
|
|
All prompts should specify commit message length requirements:
|
|
- **Soft limit**: ~50 characters (ideal length for first line)
|
|
- **Hard limit**: 76 characters (must not exceed)
|
|
|
|
Example instruction for prompt.md:
|
|
```
|
|
## Commit Format
|
|
|
|
First line: Short summary ending with a dot (aim for ~50 chars, max 76 chars)
|
|
|
|
<Optional body with details, also ending with a dot.>
|
|
|
|
IMPORTANT: Never try to commit files in .ai/
|
|
```
|
|
|
|
**tasks.json** format:
|
|
```json
|
|
{
|
|
"tasks": [
|
|
{
|
|
"id": "task-id",
|
|
"title": "Short task title",
|
|
"description": "Detailed description of what to do",
|
|
"started": false,
|
|
"completed": false,
|
|
"dependencies": ["other-task-id"]
|
|
}
|
|
]
|
|
}
|
|
```
|
|
|
|
### 4. Iterate with the User
|
|
|
|
After creating initial files, the user may want to:
|
|
- Add more tasks to tasks.json
|
|
- Refine the prompt with more details
|
|
- Add examples or patterns
|
|
- Clarify instructions
|
|
|
|
Keep refining until the user is satisfied.
|
|
|
|
## Arguments
|
|
|
|
If `$ARGUMENTS` is provided, it's the feature name to use:
|
|
- `$ARGUMENTS` = "$ARGUMENTS"
|
|
|
|
If empty, you'll need to determine/suggest a name based on the discussion.
|
|
|
|
## Examples
|
|
|
|
### Example 1: Settings Migration
|
|
```
|
|
/taskplanner settings-upgrade
|
|
```
|
|
Creates `.ai/settings-upgrade/` with prompt and tasks for migrating settings sections.
|
|
|
|
### Example 2: Open-ended
|
|
```
|
|
/taskplanner
|
|
```
|
|
Starts a conversation to understand what needs to be automated, then creates the appropriate folder.
|
|
|
|
## Starting Point
|
|
|
|
Let's begin! Please describe:
|
|
1. What repetitive coding task do you want to automate?
|
|
2. What is the end goal?
|
|
3. Do you have initial tasks in mind, or should we discover them together?
|