phpinfo/pflow-skills · Archived

pflow-task-next

Takes the next mdtodo task into progress and creates a git branch named for it. Invoked manually only.

First seen Jun 6, 2026

Installation

$ npx skills add phpinfo/pflow-skills --skill pflow-task-next

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from phpinfo/pflow-skills · top by installs.

npx skills add phpinfo/pflow-skills

Browse all from phpinfo/pflow-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

License LICENSE
Default branch master
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT
Allowed toolsBash(.agents/skills/pflow-task-next/scripts/task-next-context.sh), Bash(.agents/skills/pflow-task-next/scripts/task-next-branch.sh:*)

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,637 B
  • docs SUMMARY.md 125 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 13 installs

SKILL.md

On any failure (non-zero exit, or "status":"error" in the JSON) print ⚠️ <error.message> and stop.

Steps

  1. Take the task. Run .agents/skills/pflow-task-next/scripts/task-next-context.sh. It prints one JSON line; act on status:

- no_tasks — tell the user there's nothing to take and stop. - error — print ⚠️ <error.message> and stop. - ready — continue with task.title and task.description.

  1. Name the branch from the task (rules below) → BRANCH = TYPE/SLUG.
  2. Create it: .agents/skills/pflow-task-next/scripts/task-next-branch.sh --branch "BRANCH". On status:created, reply:

``text ✅ Task in progress: <task.title> Branch: <branch> (from <previous_branch>) ``

Branch naming

  • TYPE — one of feature (new functionality), fix (bug fix), chore (maintenance).
  • SLUG — short kebab-case English summary of the task title, git-safe (a-z0-9-).
  • Result: TYPE/SLUG, e.g. feature/login-form.

Gotchas

  • The context script requires a clean working tree on the dev branch (PFLOWGITDEV_BRANCH, default dev) and no task already in progress — otherwise it errors.
  • mdtodo take already marked the task [~]; that working-tree change is carried onto the new branch and committed later by pflow-task-finish.