agentleFS
Sign inStart free
BlakeemBlakeem/aipromptguide-workflows/skills/develop/SKILL.md

develop

Skill1 starsChanged 8 days agoMITView on GitHub

Run the AIPG develop workflow, which builds the todo blocks of approved plan files in feature, section and fix modes, then lands the accepted work on the current branch, staged or committed. It also works the project's backlog with the user. Use only when the user explicitly asks for the AIPG develop workflow.

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use scope, sync and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • YuriNachosSkill

    scope

    Configure claude-scope status line widgets for Claude Code. Use when user wants to customize widgets, change theme, reorder elements, or modify display style.

    Also in 6 projects that use this

  • MicrosoftSkill

    sync

    Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.

    Also in 6 projects that use this

  • nicolasestremSkill

    document

    Create focused documentation for specific components or features

    Also in 5 projects that use this

  • kt057Skill

    check

    lint, typecheck, test を一括実行して結果をサマリーする

    Also in 5 projects that use this

  • Harut8Skill

    architect

    Also in 9 projects that use this

  • Microsoft AzureSkill

    test

    Also in 6 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ${CLAUDE_PLUGIN_ROOT}/workflows/develop/CLAUDE.md and follow it exactly.

    line 19
  2. Very specific:

    When the task is to work the project's backlog, work only the steps its ## 0.

    line 20
  3. Distinctive:

    Use these paths wherever the guide says "this checkout" or "the tool's own directory":

    line 23

“Common” is measured: kept by at least 6 in 10 of the 23 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

The user wants to run the develop-cycle dynamic workflow on the task below.

First, before any step of the guide, run the setup check node "${CLAUDE_PLUGIN_ROOT}/tools/onboard.mjs" check --root "${CLAUDE_PLUGIN_DATA}" --repo <target.repo>, where <target.repo> is the repo the run works on. When the task does not name that repo, ask the user for it, since the working directory may be another repo. On ready, go on. On ask, ask the questions it prints in one AskUserQuestion call and run the save command it prints with the answers. The save prints ready once nothing is missing. When either command exits 1, show the user its message, which names the cause, and run it again once the cause is fixed. The Workflow tool launches only engines the session can read, which is what the access question settles. When the user declines it, the user runs the /add-dir command that question names for this session, and you pass --access session to the save and to each later check in this session. A user who declines both gets no run, since the Workflow tool cannot read the engine.

Read ${CLAUDE_PLUGIN_ROOT}/workflows/develop/CLAUDE.md and follow it exactly. When the task is to work the project's backlog, work only the steps its ## 0. Checklist names for a session that only works the backlog. Otherwise, work its ## 0. Checklist top to bottom. Use these paths wherever the guide says "this checkout" or "the tool's own directory":

  • Engine scriptPath: ${CLAUDE_PLUGIN_ROOT}/workflows/develop/develop-cycle.mjs
  • root arg: ${CLAUDE_PLUGIN_DATA}. Runs land in its runs/<runId>/, plan files in its plans/<runId>/. Never the plugin install dir, which is version-swapped on update.
  • blockTool arg: the args tool below prints it, so the spread args carry it, and the engine throws without it. Never pass it by hand.
  • Args tool (operator-side, before every launch, also applies finished runs' statuses): ${CLAUDE_PLUGIN_ROOT}/tools/plan-edit.mjs
  • Onboarding tool (operator-side): ${CLAUDE_PLUGIN_ROOT}/tools/onboard.mjs
  • Project-settings tool (operator-side): ${CLAUDE_PLUGIN_ROOT}/tools/project-settings.mjs
  • Worktree tool (operator-side): ${CLAUDE_PLUGIN_ROOT}/tools/wt.mjs

$ARGUMENTS

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free