AI SummaryStart Task is a workflow booster that initiates work on a task by validating its existence, reading task metadata, and preparing the development environment. It's useful for developers managing structured task-based projects with organized PM directories.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "Start Task" skill in my project. Please run this command in my terminal: # Install skill into the correct directory (9 files) mkdir -p .claude/skills/commands && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/commands/SKILL.md "https://raw.githubusercontent.com/FlojoInc/FloImg/main/.claude/commands/s.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/commands/c.md "https://raw.githubusercontent.com/FlojoInc/FloImg/main/.claude/commands/c.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/commands/ctx.md "https://raw.githubusercontent.com/FlojoInc/FloImg/main/.claude/commands/ctx.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/commands/gh.md "https://raw.githubusercontent.com/FlojoInc/FloImg/main/.claude/commands/gh.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/commands/p.md "https://raw.githubusercontent.com/FlojoInc/FloImg/main/.claude/commands/p.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/commands/st.md "https://raw.githubusercontent.com/FlojoInc/FloImg/main/.claude/commands/st.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/commands/sync-roadmap.md "https://raw.githubusercontent.com/FlojoInc/FloImg/main/.claude/commands/sync-roadmap.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/commands/w.md "https://raw.githubusercontent.com/FlojoInc/FloImg/main/.claude/commands/w.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/commands/x.md "https://raw.githubusercontent.com/FlojoInc/FloImg/main/.claude/commands/x.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Start working on a task
Start Task
The user wants to start working on a task. Check <command-args> for the task ID. If no task ID provided, check PROJECT_STATUS.md for the next task in "Next Up".
Steps
• Validate task exists: `bash # Check tasks folder ls vault/pm/tasks/ | grep "{TASK-ID}" # Or bugs folder ls vault/pm/bugs/ | grep "{TASK-ID}" ` • If not found, abort with: "Task {ID} not found. Use /p to create it." • Read task file to understand the work: • Get description, acceptance criteria • Check for dependencies (blocked by) • Check if subtask: • If ID contains dots (e.g., T-2025-001.1), it's a subtask • Subtasks use parent's branch - skip branch creation • Create feature branch (root tasks only): `bash # Determine branch prefix based on type # Task: feat/ # Bug: fix/ git checkout -b {prefix}/{ID}-{slug} ` • Update task status: • Change status to in-progress in frontmatter • Update updated date • Update PROJECT_STATUS.md: • Move task to "Current Focus" section • Mark as IN PROGRESS • Update "Last Updated" timestamp • Update context doc (if exists): • Change Status from "Planning" to "In Progress" • Add session start note • Commit status changes: `bash git add vault/pm/ PROJECT_STATUS.md git commit -m "chore: start {ID} Begin work on: {Title}" ` • Output summary: ` Started {ID}: {Title} Branch: {prefix}/{ID}-{slug} Status: in-progress Task file: vault/pm/{folder}/{ID}-{slug}.md Context: vault/pm/_context/{ID}-context.md Acceptance Criteria: • [ ] Criterion 1 • [ ] Criterion 2 ... Ready to implement. Use /ctx to record decisions. `
Important Rules
• Always update status in both task file and PROJECT_STATUS.md • Create branch for root tasks (not subtasks) • Commit status changes before starting work • Show acceptance criteria so goals are clear • Subtasks work on parent's branch - no new branch needed
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster