Skip to content

Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle#39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JPDuchesne merged 1 commit into from
Jul 18, 2026
Merged

Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle #39

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -291,7 +291,7 @@ Custom integrations implement `Dev::Deps::Integration` (with `install_all(pins,
- **`dev cred get <namespace> <key>`** — resolve a credential through the provider chain (ENV → keychain → file → prompt) and print it. A non-interactive miss errors with `gh secret set` guidance. Mirrors `dev deps path` for shell consumers (e.g. a staging sync).
- **`dev cache gc [--keep N]`** — reclaim host caches dev owns (see below).
- **`dev reset-container`** — remove the persistent build container (clears its incremental cache); registered only when `build.container.persist` is set.
- **`dev plan …`** — sync Cursor plans with GitHub issues (ai-flow): the issue is the canonical plan, the local `.cursor/plans/gh-<n>-<slug>.plan.md` is a transient working copy carrying an `<!-- ai-flow … -->` header. Subcommands: `new "<title>" [--org]` (create issue + linked plan), `link <n> [<file>]` / `link <file>` (attach a draft to an existing issue / create one from it), `pull <n> [--merge]` (fetch, 3-way merging when both sides changed — the merge base lives at `~/.local/state/ai-flow/`), `push [<file>]` (guarded body PATCH — refuses to clobber newer remote edits), and `status` (clean / ahead / behind / diverged, per linked plan). `--org` targets the org plans repo (`plans_repo:` in `~/.config/dev/config.yml`, or `DEV_PLANS_REPO`) instead of the current repo's origin. Every invocation also ensures `~/.cursor/skills/ai-flow` symlinks to the skill shipped in `share/cursor-skills/`, so the Cursor agent knows these verbs. For auto-push, a participating repo adds a Cursor `afterFileEdit` hook to `.cursor/hooks.json` running `dev plan hook-after-edit` — it reads the hook payload from stdin and no-ops unless the edited file is a linked plan.
- **`dev plan …`** — sync Cursor plans with GitHub issues (ai-flow): the issue is the canonical plan, the local `.cursor/plans/gh-<n>-<slug>.plan.md` is a transient working copy carrying an `<!-- ai-flow … -->` header. Subcommands: `new "<title>" [--org]` (create issue + linked plan; `--org` scaffolds a `Target repos:` line), `link <n> [<file>]` / `link <file>` (attach a draft to an existing issue / create one from it), `pull <n> [--merge]` (fetch, 3-way merging when both sides changed — the merge base lives at `~/.local/state/ai-flow/`), `push [<file>]` (guarded body PATCH — refuses to clobber newer remote edits), and `status` (clean / ahead / behind / diverged, per linked plan). `--org` targets the org plans repo (`plans_repo:` in `~/.config/dev/config.yml`, or `DEV_PLANS_REPO`) instead of the current repo's origin. Every invocation also ensures `~/.cursor/skills/ai-flow` symlinks to the skill shipped in `share/cursor-skills/`, so the Cursor agent knows these verbs. For auto-push, a participating repo adds a Cursor `afterFileEdit` hook to `.cursor/hooks.json` running `dev plan hook-after-edit` — it reads the hook payload from stdin and no-ops unless the edited file is a linked plan. What happens to a plan after it's canonical — `/ask`, `/edit`, `/split` (two-phase dry/apply), `/build` — is ai-flow's remote half: see [plan-lifecycle.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/plan-lifecycle.md) and [commands.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/commands.md).

## Build container & caching model

Expand Down
5 changes: 5 additions & 0 deletions lib/dev/plan/accessor.rb
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -67,13 +67,18 @@ def run(args, out: $stdout, input: $stdin)

# `dev plan new "<title>" [--org]` — create the issue first (it is
# canonical from birth), then materialize the linked local working copy.
# Org plans are scaffolded with a `Target repos:` line: they usually
# span repos, and the line narrows /split's routing menu (see ai-flow's
# docs/plan-lifecycle.md). Left blank it is inert — the menu falls back
# to every org repo.
def new_plan(args, out:)
org = args.delete("--org") ? true : false
title = args.shift
raise UsageError, "usage: dev plan new \"<title>\" [--org]" if title.nil? || title.empty? || !args.empty?

owner_repo = target_repo(org:)
body = "# #{title}\n"
body += "\nTarget repos:\n<!-- comma-separated owner/repo list — declares scope; /split routes sub-issues within it -->\n" if org
issue = @issues.create(owner_repo, title: title, body: Plan.to_issue_body(body))
path = write_linked_plan(owner_repo, issue, body)
out.puts "dev: created #{owner_repo}##{issue.number} (#{issue.html_url})"
Expand Down
23 changes: 23 additions & 0 deletions share/cursor-skills/ai-flow/SKILL.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -27,6 +27,29 @@ conflict guard so local content can never clobber newer remote edits.
| "address the open feedback on this plan" | see below |
| org-wide / cross-repo plan (not tied to this repo) | add `--org` to `new`/`link`/`pull` — targets the configured org plans repo |

## Multi-repo plans: the `Target repos:` line

When canonizing a plan whose work lands in other repos (especially
`dev plan link --org`), include a `Target repos: owner/a, owner/b` line near
the top of the plan body. It declares the plan's scope and narrows the repo
menu `/split` routes sub-issues within (`dev plan new --org` scaffolds the
line; fill it in). Without it, `/split` may route to any repo of the org.

## Remote lifecycle (the GitHub-side commands)

Once canonical, the plan is driven from GitHub comments — `/ask` and `/edit`
refine the body, `/split --dry` stages an editable `## Subtasks` yaml
section in the plan body (review/edit it, then `/split --apply`; bare
`/split` does both), `/build` builds a PR (or iterates when commented on a
PR), `/build --split` orchestrates the sub-issues in dependency waves. A
staged (unapplied) `## Subtasks` spec blocks `/build` until applied or
deleted; the section round-trips through `dev plan pull`/`push` like any
other body content. Full reference:
[docs/commands.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/commands.md)
and
[docs/plan-lifecycle.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/plan-lifecycle.md)
in d3mlabs/ai-flow.

## Addressing open feedback

Open feedback lives as issue comments (often quote-anchored). To address it:
Expand Down
6 changes: 4 additions & 2 deletions test/dev/plan/accessor_test.rb
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -115,10 +115,12 @@ def read_plan(root, name)
When "creating an org-wide plan"
accessor.run(["new", "Org roadmap", "--org"], out: StringIO.new)

Then "the issue lands in the plans repo and the filename disambiguates"
Then "the issue lands in the plans repo, scaffolded with a Target repos line, and the filename disambiguates"
issues.get("d3mlabs/plans", 1).title == "Org roadmap"
header, _body = read_plan(root, "gh-plans-1-org-roadmap.plan.md")
issues.get("d3mlabs/plans", 1).body.include?("Target repos:")
header, body = read_plan(root, "gh-plans-1-org-roadmap.plan.md")
header.owner_repo == "d3mlabs/plans"
body.include?("Target repos:")

Cleanup
FileUtils.rm_rf(dir)
Expand Down
Loading
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle by JPDuchesne · Pull Request #39 · d3mlabs/dev · GitHub
Skip to content
Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle#39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

JPDuchesne
merged 1 commit into

from

Jul 18, 2026
 Merged


Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle
#39
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


2 changes: 1 addition & 1 deletion
README.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -291,7 +291,7 @@ Custom integrations implement `Dev::Deps::Integration` (with `install_all(pins,
- **`dev cred get <namespace> <key>`** — resolve a credential through the provider chain (ENV → keychain → file → prompt) and print it. A non-interactive miss errors with `gh secret set` guidance. Mirrors `dev deps path` for shell consumers (e.g. a staging sync).
- **`dev cache gc [--keep N]`** — reclaim host caches dev owns (see below).
- **`dev reset-container`** — remove the persistent build container (clears its incremental cache); registered only when `build.container.persist` is set.
- **`dev plan …`** — sync Cursor plans with GitHub issues (ai-flow): the issue is the canonical plan, the local `.cursor/plans/gh-<n>-<slug>.plan.md` is a transient working copy carrying an `<!-- ai-flow … -->` header. Subcommands: `new "<title>" [--org]` (create issue + linked plan), `link <n> [<file>]` / `link <file>` (attach a draft to an existing issue / create one from it), `pull <n> [--merge]` (fetch, 3-way merging when both sides changed — the merge base lives at `~/.local/state/ai-flow/`), `push [<file>]` (guarded body PATCH — refuses to clobber newer remote edits), and `status` (clean / ahead / behind / diverged, per linked plan). `--org` targets the org plans repo (`plans_repo:` in `~/.config/dev/config.yml`, or `DEV_PLANS_REPO`) instead of the current repo's origin. Every invocation also ensures `~/.cursor/skills/ai-flow` symlinks to the skill shipped in `share/cursor-skills/`, so the Cursor agent knows these verbs. For auto-push, a participating repo adds a Cursor `afterFileEdit` hook to `.cursor/hooks.json` running `dev plan hook-after-edit` — it reads the hook payload from stdin and no-ops unless the edited file is a linked plan.
- **`dev plan …`** — sync Cursor plans with GitHub issues (ai-flow): the issue is the canonical plan, the local `.cursor/plans/gh-<n>-<slug>.plan.md` is a transient working copy carrying an `<!-- ai-flow … -->` header. Subcommands: `new "<title>" [--org]` (create issue + linked plan; `--org` scaffolds a `Target repos:` line), `link <n> [<file>]` / `link <file>` (attach a draft to an existing issue / create one from it), `pull <n> [--merge]` (fetch, 3-way merging when both sides changed — the merge base lives at `~/.local/state/ai-flow/`), `push [<file>]` (guarded body PATCH — refuses to clobber newer remote edits), and `status` (clean / ahead / behind / diverged, per linked plan). `--org` targets the org plans repo (`plans_repo:` in `~/.config/dev/config.yml`, or `DEV_PLANS_REPO`) instead of the current repo's origin. Every invocation also ensures `~/.cursor/skills/ai-flow` symlinks to the skill shipped in `share/cursor-skills/`, so the Cursor agent knows these verbs. For auto-push, a participating repo adds a Cursor `afterFileEdit` hook to `.cursor/hooks.json` running `dev plan hook-after-edit` — it reads the hook payload from stdin and no-ops unless the edited file is a linked plan. What happens to a plan after it's canonical — `/ask`, `/edit`, `/split` (two-phase dry/apply), `/build` — is ai-flow's remote half: see [plan-lifecycle.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/plan-lifecycle.md) and [commands.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/commands.md).

## Build container & caching model

Expand Down

5 changes: 5 additions & 0 deletions
lib/dev/plan/accessor.rb

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -67,13 +67,18 @@ def run(args, out: $stdout, input: $stdin)

 # `dev plan new "<title>" [--org]` — create the issue first (it is
 # canonical from birth), then materialize the linked local working copy.
 # Org plans are scaffolded with a `Target repos:` line: they usually
 # span repos, and the line narrows /split's routing menu (see ai-flow's
 # docs/plan-lifecycle.md). Left blank it is inert — the menu falls back
 # to every org repo.
 def new_plan(args, out:)
 org = args.delete("--org") ? true : false
 title = args.shift
 raise UsageError, "usage: dev plan new \"<title>\" [--org]" if title.nil? || title.empty? || !args.empty?

 owner_repo = target_repo(org:)
 body = "# #{title}\n"
 body += "\nTarget repos:\n<!-- comma-separated owner/repo list — declares scope; /split routes sub-issues within it -->\n" if org
 issue = @issues.create(owner_repo, title: title, body: Plan.to_issue_body(body))
 path = write_linked_plan(owner_repo, issue, body)
 out.puts "dev: created #{owner_repo}##{issue.number} (#{issue.html_url})"
Expand Down

23 changes: 23 additions & 0 deletions
share/cursor-skills/ai-flow/SKILL.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -27,6 +27,29 @@ conflict guard so local content can never clobber newer remote edits.
| "address the open feedback on this plan" | see below |
| org-wide / cross-repo plan (not tied to this repo) | add `--org` to `new`/`link`/`pull` — targets the configured org plans repo |

## Multi-repo plans: the `Target repos:` line

When canonizing a plan whose work lands in other repos (especially
`dev plan link --org`), include a `Target repos: owner/a, owner/b` line near
the top of the plan body. It declares the plan's scope and narrows the repo
menu `/split` routes sub-issues within (`dev plan new --org` scaffolds the
line; fill it in). Without it, `/split` may route to any repo of the org.

## Remote lifecycle (the GitHub-side commands)

Once canonical, the plan is driven from GitHub comments — `/ask` and `/edit`
refine the body, `/split --dry` stages an editable `## Subtasks` yaml
section in the plan body (review/edit it, then `/split --apply`; bare
`/split` does both), `/build` builds a PR (or iterates when commented on a
PR), `/build --split` orchestrates the sub-issues in dependency waves. A
staged (unapplied) `## Subtasks` spec blocks `/build` until applied or
deleted; the section round-trips through `dev plan pull`/`push` like any
other body content. Full reference:
[docs/commands.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/commands.md)
and
[docs/plan-lifecycle.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/plan-lifecycle.md)
in d3mlabs/ai-flow.

## Addressing open feedback

Open feedback lives as issue comments (often quote-anchored). To address it:
Expand Down

6 changes: 4 additions & 2 deletions
test/dev/plan/accessor_test.rb

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -115,10 +115,12 @@ def read_plan(root, name)
 When "creating an org-wide plan"
 accessor.run(["new", "Org roadmap", "--org"], out: StringIO.new)

 Then "the issue lands in the plans repo and the filename disambiguates"
 Then "the issue lands in the plans repo, scaffolded with a Target repos line, and the filename disambiguates"
 issues.get("d3mlabs/plans", 1).title == "Org roadmap"
 header, _body = read_plan(root, "gh-plans-1-org-roadmap.plan.md")
 issues.get("d3mlabs/plans", 1).body.include?("Target repos:")
 header, body = read_plan(root, "gh-plans-1-org-roadmap.plan.md")
 header.owner_repo == "d3mlabs/plans"
 body.include?("Target repos:")

 Cleanup
 FileUtils.rm_rf(dir)
Expand Down
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle by JPDuchesne · Pull Request #39 · d3mlabs/dev · GitHub
Skip to content
Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle#39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

JPDuchesne
merged 1 commit into

from

Jul 18, 2026
 Merged


Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle
#39
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


2 changes: 1 addition & 1 deletion
README.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -291,7 +291,7 @@ Custom integrations implement `Dev::Deps::Integration` (with `install_all(pins,
- **`dev cred get <namespace> <key>`** — resolve a credential through the provider chain (ENV → keychain → file → prompt) and print it. A non-interactive miss errors with `gh secret set` guidance. Mirrors `dev deps path` for shell consumers (e.g. a staging sync).
- **`dev cache gc [--keep N]`** — reclaim host caches dev owns (see below).
- **`dev reset-container`** — remove the persistent build container (clears its incremental cache); registered only when `build.container.persist` is set.
- **`dev plan …`** — sync Cursor plans with GitHub issues (ai-flow): the issue is the canonical plan, the local `.cursor/plans/gh-<n>-<slug>.plan.md` is a transient working copy carrying an `<!-- ai-flow … -->` header. Subcommands: `new "<title>" [--org]` (create issue + linked plan), `link <n> [<file>]` / `link <file>` (attach a draft to an existing issue / create one from it), `pull <n> [--merge]` (fetch, 3-way merging when both sides changed — the merge base lives at `~/.local/state/ai-flow/`), `push [<file>]` (guarded body PATCH — refuses to clobber newer remote edits), and `status` (clean / ahead / behind / diverged, per linked plan). `--org` targets the org plans repo (`plans_repo:` in `~/.config/dev/config.yml`, or `DEV_PLANS_REPO`) instead of the current repo's origin. Every invocation also ensures `~/.cursor/skills/ai-flow` symlinks to the skill shipped in `share/cursor-skills/`, so the Cursor agent knows these verbs. For auto-push, a participating repo adds a Cursor `afterFileEdit` hook to `.cursor/hooks.json` running `dev plan hook-after-edit` — it reads the hook payload from stdin and no-ops unless the edited file is a linked plan.
- **`dev plan …`** — sync Cursor plans with GitHub issues (ai-flow): the issue is the canonical plan, the local `.cursor/plans/gh-<n>-<slug>.plan.md` is a transient working copy carrying an `<!-- ai-flow … -->` header. Subcommands: `new "<title>" [--org]` (create issue + linked plan; `--org` scaffolds a `Target repos:` line), `link <n> [<file>]` / `link <file>` (attach a draft to an existing issue / create one from it), `pull <n> [--merge]` (fetch, 3-way merging when both sides changed — the merge base lives at `~/.local/state/ai-flow/`), `push [<file>]` (guarded body PATCH — refuses to clobber newer remote edits), and `status` (clean / ahead / behind / diverged, per linked plan). `--org` targets the org plans repo (`plans_repo:` in `~/.config/dev/config.yml`, or `DEV_PLANS_REPO`) instead of the current repo's origin. Every invocation also ensures `~/.cursor/skills/ai-flow` symlinks to the skill shipped in `share/cursor-skills/`, so the Cursor agent knows these verbs. For auto-push, a participating repo adds a Cursor `afterFileEdit` hook to `.cursor/hooks.json` running `dev plan hook-after-edit` — it reads the hook payload from stdin and no-ops unless the edited file is a linked plan. What happens to a plan after it's canonical — `/ask`, `/edit`, `/split` (two-phase dry/apply), `/build` — is ai-flow's remote half: see [plan-lifecycle.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/plan-lifecycle.md) and [commands.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/commands.md).

## Build container & caching model

Expand Down

5 changes: 5 additions & 0 deletions
lib/dev/plan/accessor.rb

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -67,13 +67,18 @@ def run(args, out: $stdout, input: $stdin)

 # `dev plan new "<title>" [--org]` — create the issue first (it is
 # canonical from birth), then materialize the linked local working copy.
 # Org plans are scaffolded with a `Target repos:` line: they usually
 # span repos, and the line narrows /split's routing menu (see ai-flow's
 # docs/plan-lifecycle.md). Left blank it is inert — the menu falls back
 # to every org repo.
 def new_plan(args, out:)
 org = args.delete("--org") ? true : false
 title = args.shift
 raise UsageError, "usage: dev plan new \"<title>\" [--org]" if title.nil? || title.empty? || !args.empty?

 owner_repo = target_repo(org:)
 body = "# #{title}\n"
 body += "\nTarget repos:\n<!-- comma-separated owner/repo list — declares scope; /split routes sub-issues within it -->\n" if org
 issue = @issues.create(owner_repo, title: title, body: Plan.to_issue_body(body))
 path = write_linked_plan(owner_repo, issue, body)
 out.puts "dev: created #{owner_repo}##{issue.number} (#{issue.html_url})"
Expand Down

23 changes: 23 additions & 0 deletions
share/cursor-skills/ai-flow/SKILL.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -27,6 +27,29 @@ conflict guard so local content can never clobber newer remote edits.
| "address the open feedback on this plan" | see below |
| org-wide / cross-repo plan (not tied to this repo) | add `--org` to `new`/`link`/`pull` — targets the configured org plans repo |

## Multi-repo plans: the `Target repos:` line

When canonizing a plan whose work lands in other repos (especially
`dev plan link --org`), include a `Target repos: owner/a, owner/b` line near
the top of the plan body. It declares the plan's scope and narrows the repo
menu `/split` routes sub-issues within (`dev plan new --org` scaffolds the
line; fill it in). Without it, `/split` may route to any repo of the org.

## Remote lifecycle (the GitHub-side commands)

Once canonical, the plan is driven from GitHub comments — `/ask` and `/edit`
refine the body, `/split --dry` stages an editable `## Subtasks` yaml
section in the plan body (review/edit it, then `/split --apply`; bare
`/split` does both), `/build` builds a PR (or iterates when commented on a
PR), `/build --split` orchestrates the sub-issues in dependency waves. A
staged (unapplied) `## Subtasks` spec blocks `/build` until applied or
deleted; the section round-trips through `dev plan pull`/`push` like any
other body content. Full reference:
[docs/commands.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/commands.md)
and
[docs/plan-lifecycle.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/plan-lifecycle.md)
in d3mlabs/ai-flow.

## Addressing open feedback

Open feedback lives as issue comments (often quote-anchored). To address it:
Expand Down

6 changes: 4 additions & 2 deletions
test/dev/plan/accessor_test.rb

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -115,10 +115,12 @@ def read_plan(root, name)
 When "creating an org-wide plan"
 accessor.run(["new", "Org roadmap", "--org"], out: StringIO.new)

 Then "the issue lands in the plans repo and the filename disambiguates"
 Then "the issue lands in the plans repo, scaffolded with a Target repos line, and the filename disambiguates"
 issues.get("d3mlabs/plans", 1).title == "Org roadmap"
 header, _body = read_plan(root, "gh-plans-1-org-roadmap.plan.md")
 issues.get("d3mlabs/plans", 1).body.include?("Target repos:")
 header, body = read_plan(root, "gh-plans-1-org-roadmap.plan.md")
 header.owner_repo == "d3mlabs/plans"
 body.include?("Target repos:")

 Cleanup
 FileUtils.rm_rf(dir)
Expand Down
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle by JPDuchesne · Pull Request #39 · d3mlabs/dev · GitHub
Skip to content
Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle#39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

JPDuchesne
merged 1 commit into

from

Jul 18, 2026
 Merged


Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle
#39
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


2 changes: 1 addition & 1 deletion
README.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -291,7 +291,7 @@ Custom integrations implement `Dev::Deps::Integration` (with `install_all(pins,
- **`dev cred get <namespace> <key>`** — resolve a credential through the provider chain (ENV → keychain → file → prompt) and print it. A non-interactive miss errors with `gh secret set` guidance. Mirrors `dev deps path` for shell consumers (e.g. a staging sync).
- **`dev cache gc [--keep N]`** — reclaim host caches dev owns (see below).
- **`dev reset-container`** — remove the persistent build container (clears its incremental cache); registered only when `build.container.persist` is set.
- **`dev plan …`** — sync Cursor plans with GitHub issues (ai-flow): the issue is the canonical plan, the local `.cursor/plans/gh-<n>-<slug>.plan.md` is a transient working copy carrying an `<!-- ai-flow … -->` header. Subcommands: `new "<title>" [--org]` (create issue + linked plan), `link <n> [<file>]` / `link <file>` (attach a draft to an existing issue / create one from it), `pull <n> [--merge]` (fetch, 3-way merging when both sides changed — the merge base lives at `~/.local/state/ai-flow/`), `push [<file>]` (guarded body PATCH — refuses to clobber newer remote edits), and `status` (clean / ahead / behind / diverged, per linked plan). `--org` targets the org plans repo (`plans_repo:` in `~/.config/dev/config.yml`, or `DEV_PLANS_REPO`) instead of the current repo's origin. Every invocation also ensures `~/.cursor/skills/ai-flow` symlinks to the skill shipped in `share/cursor-skills/`, so the Cursor agent knows these verbs. For auto-push, a participating repo adds a Cursor `afterFileEdit` hook to `.cursor/hooks.json` running `dev plan hook-after-edit` — it reads the hook payload from stdin and no-ops unless the edited file is a linked plan.
- **`dev plan …`** — sync Cursor plans with GitHub issues (ai-flow): the issue is the canonical plan, the local `.cursor/plans/gh-<n>-<slug>.plan.md` is a transient working copy carrying an `<!-- ai-flow … -->` header. Subcommands: `new "<title>" [--org]` (create issue + linked plan; `--org` scaffolds a `Target repos:` line), `link <n> [<file>]` / `link <file>` (attach a draft to an existing issue / create one from it), `pull <n> [--merge]` (fetch, 3-way merging when both sides changed — the merge base lives at `~/.local/state/ai-flow/`), `push [<file>]` (guarded body PATCH — refuses to clobber newer remote edits), and `status` (clean / ahead / behind / diverged, per linked plan). `--org` targets the org plans repo (`plans_repo:` in `~/.config/dev/config.yml`, or `DEV_PLANS_REPO`) instead of the current repo's origin. Every invocation also ensures `~/.cursor/skills/ai-flow` symlinks to the skill shipped in `share/cursor-skills/`, so the Cursor agent knows these verbs. For auto-push, a participating repo adds a Cursor `afterFileEdit` hook to `.cursor/hooks.json` running `dev plan hook-after-edit` — it reads the hook payload from stdin and no-ops unless the edited file is a linked plan. What happens to a plan after it's canonical — `/ask`, `/edit`, `/split` (two-phase dry/apply), `/build` — is ai-flow's remote half: see [plan-lifecycle.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/plan-lifecycle.md) and [commands.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/commands.md).

## Build container & caching model

Expand Down

5 changes: 5 additions & 0 deletions
lib/dev/plan/accessor.rb

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -67,13 +67,18 @@ def run(args, out: $stdout, input: $stdin)

 # `dev plan new "<title>" [--org]` — create the issue first (it is
 # canonical from birth), then materialize the linked local working copy.
 # Org plans are scaffolded with a `Target repos:` line: they usually
 # span repos, and the line narrows /split's routing menu (see ai-flow's
 # docs/plan-lifecycle.md). Left blank it is inert — the menu falls back
 # to every org repo.
 def new_plan(args, out:)
 org = args.delete("--org") ? true : false
 title = args.shift
 raise UsageError, "usage: dev plan new \"<title>\" [--org]" if title.nil? || title.empty? || !args.empty?

 owner_repo = target_repo(org:)
 body = "# #{title}\n"
 body += "\nTarget repos:\n<!-- comma-separated owner/repo list — declares scope; /split routes sub-issues within it -->\n" if org
 issue = @issues.create(owner_repo, title: title, body: Plan.to_issue_body(body))
 path = write_linked_plan(owner_repo, issue, body)
 out.puts "dev: created #{owner_repo}##{issue.number} (#{issue.html_url})"
Expand Down

23 changes: 23 additions & 0 deletions
share/cursor-skills/ai-flow/SKILL.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -27,6 +27,29 @@ conflict guard so local content can never clobber newer remote edits.
| "address the open feedback on this plan" | see below |
| org-wide / cross-repo plan (not tied to this repo) | add `--org` to `new`/`link`/`pull` — targets the configured org plans repo |

## Multi-repo plans: the `Target repos:` line

When canonizing a plan whose work lands in other repos (especially
`dev plan link --org`), include a `Target repos: owner/a, owner/b` line near
the top of the plan body. It declares the plan's scope and narrows the repo
menu `/split` routes sub-issues within (`dev plan new --org` scaffolds the
line; fill it in). Without it, `/split` may route to any repo of the org.

## Remote lifecycle (the GitHub-side commands)

Once canonical, the plan is driven from GitHub comments — `/ask` and `/edit`
refine the body, `/split --dry` stages an editable `## Subtasks` yaml
section in the plan body (review/edit it, then `/split --apply`; bare
`/split` does both), `/build` builds a PR (or iterates when commented on a
PR), `/build --split` orchestrates the sub-issues in dependency waves. A
staged (unapplied) `## Subtasks` spec blocks `/build` until applied or
deleted; the section round-trips through `dev plan pull`/`push` like any
other body content. Full reference:
[docs/commands.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/commands.md)
and
[docs/plan-lifecycle.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/plan-lifecycle.md)
in d3mlabs/ai-flow.

## Addressing open feedback

Open feedback lives as issue comments (often quote-anchored). To address it:
Expand Down

6 changes: 4 additions & 2 deletions
test/dev/plan/accessor_test.rb

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -115,10 +115,12 @@ def read_plan(root, name)
 When "creating an org-wide plan"
 accessor.run(["new", "Org roadmap", "--org"], out: StringIO.new)

 Then "the issue lands in the plans repo and the filename disambiguates"
 Then "the issue lands in the plans repo, scaffolded with a Target repos line, and the filename disambiguates"
 issues.get("d3mlabs/plans", 1).title == "Org roadmap"
 header, _body = read_plan(root, "gh-plans-1-org-roadmap.plan.md")
 issues.get("d3mlabs/plans", 1).body.include?("Target repos:")
 header, body = read_plan(root, "gh-plans-1-org-roadmap.plan.md")
 header.owner_repo == "d3mlabs/plans"
 body.include?("Target repos:")

 Cleanup
 FileUtils.rm_rf(dir)
Expand Down
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle by JPDuchesne · Pull Request #39 · d3mlabs/dev · GitHub
Skip to content
Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle#39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

JPDuchesne
merged 1 commit into

from

Jul 18, 2026
 Merged


Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle
#39
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


2 changes: 1 addition & 1 deletion
README.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -291,7 +291,7 @@ Custom integrations implement `Dev::Deps::Integration` (with `install_all(pins,
- **`dev cred get <namespace> <key>`** — resolve a credential through the provider chain (ENV → keychain → file → prompt) and print it. A non-interactive miss errors with `gh secret set` guidance. Mirrors `dev deps path` for shell consumers (e.g. a staging sync).
- **`dev cache gc [--keep N]`** — reclaim host caches dev owns (see below).
- **`dev reset-container`** — remove the persistent build container (clears its incremental cache); registered only when `build.container.persist` is set.
- **`dev plan …`** — sync Cursor plans with GitHub issues (ai-flow): the issue is the canonical plan, the local `.cursor/plans/gh-<n>-<slug>.plan.md` is a transient working copy carrying an `<!-- ai-flow … -->` header. Subcommands: `new "<title>" [--org]` (create issue + linked plan), `link <n> [<file>]` / `link <file>` (attach a draft to an existing issue / create one from it), `pull <n> [--merge]` (fetch, 3-way merging when both sides changed — the merge base lives at `~/.local/state/ai-flow/`), `push [<file>]` (guarded body PATCH — refuses to clobber newer remote edits), and `status` (clean / ahead / behind / diverged, per linked plan). `--org` targets the org plans repo (`plans_repo:` in `~/.config/dev/config.yml`, or `DEV_PLANS_REPO`) instead of the current repo's origin. Every invocation also ensures `~/.cursor/skills/ai-flow` symlinks to the skill shipped in `share/cursor-skills/`, so the Cursor agent knows these verbs. For auto-push, a participating repo adds a Cursor `afterFileEdit` hook to `.cursor/hooks.json` running `dev plan hook-after-edit` — it reads the hook payload from stdin and no-ops unless the edited file is a linked plan.
- **`dev plan …`** — sync Cursor plans with GitHub issues (ai-flow): the issue is the canonical plan, the local `.cursor/plans/gh-<n>-<slug>.plan.md` is a transient working copy carrying an `<!-- ai-flow … -->` header. Subcommands: `new "<title>" [--org]` (create issue + linked plan; `--org` scaffolds a `Target repos:` line), `link <n> [<file>]` / `link <file>` (attach a draft to an existing issue / create one from it), `pull <n> [--merge]` (fetch, 3-way merging when both sides changed — the merge base lives at `~/.local/state/ai-flow/`), `push [<file>]` (guarded body PATCH — refuses to clobber newer remote edits), and `status` (clean / ahead / behind / diverged, per linked plan). `--org` targets the org plans repo (`plans_repo:` in `~/.config/dev/config.yml`, or `DEV_PLANS_REPO`) instead of the current repo's origin. Every invocation also ensures `~/.cursor/skills/ai-flow` symlinks to the skill shipped in `share/cursor-skills/`, so the Cursor agent knows these verbs. For auto-push, a participating repo adds a Cursor `afterFileEdit` hook to `.cursor/hooks.json` running `dev plan hook-after-edit` — it reads the hook payload from stdin and no-ops unless the edited file is a linked plan. What happens to a plan after it's canonical — `/ask`, `/edit`, `/split` (two-phase dry/apply), `/build` — is ai-flow's remote half: see [plan-lifecycle.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/plan-lifecycle.md) and [commands.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/commands.md).

## Build container & caching model

Expand Down

5 changes: 5 additions & 0 deletions
lib/dev/plan/accessor.rb

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -67,13 +67,18 @@ def run(args, out: $stdout, input: $stdin)

 # `dev plan new "<title>" [--org]` — create the issue first (it is
 # canonical from birth), then materialize the linked local working copy.
 # Org plans are scaffolded with a `Target repos:` line: they usually
 # span repos, and the line narrows /split's routing menu (see ai-flow's
 # docs/plan-lifecycle.md). Left blank it is inert — the menu falls back
 # to every org repo.
 def new_plan(args, out:)
 org = args.delete("--org") ? true : false
 title = args.shift
 raise UsageError, "usage: dev plan new \"<title>\" [--org]" if title.nil? || title.empty? || !args.empty?

 owner_repo = target_repo(org:)
 body = "# #{title}\n"
 body += "\nTarget repos:\n<!-- comma-separated owner/repo list — declares scope; /split routes sub-issues within it -->\n" if org
 issue = @issues.create(owner_repo, title: title, body: Plan.to_issue_body(body))
 path = write_linked_plan(owner_repo, issue, body)
 out.puts "dev: created #{owner_repo}##{issue.number} (#{issue.html_url})"
Expand Down

23 changes: 23 additions & 0 deletions
share/cursor-skills/ai-flow/SKILL.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -27,6 +27,29 @@ conflict guard so local content can never clobber newer remote edits.
| "address the open feedback on this plan" | see below |
| org-wide / cross-repo plan (not tied to this repo) | add `--org` to `new`/`link`/`pull` — targets the configured org plans repo |

## Multi-repo plans: the `Target repos:` line

When canonizing a plan whose work lands in other repos (especially
`dev plan link --org`), include a `Target repos: owner/a, owner/b` line near
the top of the plan body. It declares the plan's scope and narrows the repo
menu `/split` routes sub-issues within (`dev plan new --org` scaffolds the
line; fill it in). Without it, `/split` may route to any repo of the org.

## Remote lifecycle (the GitHub-side commands)

Once canonical, the plan is driven from GitHub comments — `/ask` and `/edit`
refine the body, `/split --dry` stages an editable `## Subtasks` yaml
section in the plan body (review/edit it, then `/split --apply`; bare
`/split` does both), `/build` builds a PR (or iterates when commented on a
PR), `/build --split` orchestrates the sub-issues in dependency waves. A
staged (unapplied) `## Subtasks` spec blocks `/build` until applied or
deleted; the section round-trips through `dev plan pull`/`push` like any
other body content. Full reference:
[docs/commands.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/commands.md)
and
[docs/plan-lifecycle.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/plan-lifecycle.md)
in d3mlabs/ai-flow.

## Addressing open feedback

Open feedback lives as issue comments (often quote-anchored). To address it:
Expand Down

6 changes: 4 additions & 2 deletions
test/dev/plan/accessor_test.rb

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -115,10 +115,12 @@ def read_plan(root, name)
 When "creating an org-wide plan"
 accessor.run(["new", "Org roadmap", "--org"], out: StringIO.new)

 Then "the issue lands in the plans repo and the filename disambiguates"
 Then "the issue lands in the plans repo, scaffolded with a Target repos line, and the filename disambiguates"
 issues.get("d3mlabs/plans", 1).title == "Org roadmap"
 header, _body = read_plan(root, "gh-plans-1-org-roadmap.plan.md")
 issues.get("d3mlabs/plans", 1).body.include?("Target repos:")
 header, body = read_plan(root, "gh-plans-1-org-roadmap.plan.md")
 header.owner_repo == "d3mlabs/plans"
 body.include?("Target repos:")

 Cleanup
 FileUtils.rm_rf(dir)
Expand Down
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle by JPDuchesne · Pull Request #39 · d3mlabs/dev · GitHub
Skip to content
Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle#39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

JPDuchesne
merged 1 commit into

from

Jul 18, 2026
 Merged


Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle
#39
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


2 changes: 1 addition & 1 deletion
README.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -291,7 +291,7 @@ Custom integrations implement `Dev::Deps::Integration` (with `install_all(pins,
- **`dev cred get <namespace> <key>`** — resolve a credential through the provider chain (ENV → keychain → file → prompt) and print it. A non-interactive miss errors with `gh secret set` guidance. Mirrors `dev deps path` for shell consumers (e.g. a staging sync).
- **`dev cache gc [--keep N]`** — reclaim host caches dev owns (see below).
- **`dev reset-container`** — remove the persistent build container (clears its incremental cache); registered only when `build.container.persist` is set.
- **`dev plan …`** — sync Cursor plans with GitHub issues (ai-flow): the issue is the canonical plan, the local `.cursor/plans/gh-<n>-<slug>.plan.md` is a transient working copy carrying an `<!-- ai-flow … -->` header. Subcommands: `new "<title>" [--org]` (create issue + linked plan), `link <n> [<file>]` / `link <file>` (attach a draft to an existing issue / create one from it), `pull <n> [--merge]` (fetch, 3-way merging when both sides changed — the merge base lives at `~/.local/state/ai-flow/`), `push [<file>]` (guarded body PATCH — refuses to clobber newer remote edits), and `status` (clean / ahead / behind / diverged, per linked plan). `--org` targets the org plans repo (`plans_repo:` in `~/.config/dev/config.yml`, or `DEV_PLANS_REPO`) instead of the current repo's origin. Every invocation also ensures `~/.cursor/skills/ai-flow` symlinks to the skill shipped in `share/cursor-skills/`, so the Cursor agent knows these verbs. For auto-push, a participating repo adds a Cursor `afterFileEdit` hook to `.cursor/hooks.json` running `dev plan hook-after-edit` — it reads the hook payload from stdin and no-ops unless the edited file is a linked plan.
- **`dev plan …`** — sync Cursor plans with GitHub issues (ai-flow): the issue is the canonical plan, the local `.cursor/plans/gh-<n>-<slug>.plan.md` is a transient working copy carrying an `<!-- ai-flow … -->` header. Subcommands: `new "<title>" [--org]` (create issue + linked plan; `--org` scaffolds a `Target repos:` line), `link <n> [<file>]` / `link <file>` (attach a draft to an existing issue / create one from it), `pull <n> [--merge]` (fetch, 3-way merging when both sides changed — the merge base lives at `~/.local/state/ai-flow/`), `push [<file>]` (guarded body PATCH — refuses to clobber newer remote edits), and `status` (clean / ahead / behind / diverged, per linked plan). `--org` targets the org plans repo (`plans_repo:` in `~/.config/dev/config.yml`, or `DEV_PLANS_REPO`) instead of the current repo's origin. Every invocation also ensures `~/.cursor/skills/ai-flow` symlinks to the skill shipped in `share/cursor-skills/`, so the Cursor agent knows these verbs. For auto-push, a participating repo adds a Cursor `afterFileEdit` hook to `.cursor/hooks.json` running `dev plan hook-after-edit` — it reads the hook payload from stdin and no-ops unless the edited file is a linked plan. What happens to a plan after it's canonical — `/ask`, `/edit`, `/split` (two-phase dry/apply), `/build` — is ai-flow's remote half: see [plan-lifecycle.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/plan-lifecycle.md) and [commands.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/commands.md).

## Build container & caching model

Expand Down

5 changes: 5 additions & 0 deletions
lib/dev/plan/accessor.rb

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -67,13 +67,18 @@ def run(args, out: $stdout, input: $stdin)

 # `dev plan new "<title>" [--org]` — create the issue first (it is
 # canonical from birth), then materialize the linked local working copy.
 # Org plans are scaffolded with a `Target repos:` line: they usually
 # span repos, and the line narrows /split's routing menu (see ai-flow's
 # docs/plan-lifecycle.md). Left blank it is inert — the menu falls back
 # to every org repo.
 def new_plan(args, out:)
 org = args.delete("--org") ? true : false
 title = args.shift
 raise UsageError, "usage: dev plan new \"<title>\" [--org]" if title.nil? || title.empty? || !args.empty?

 owner_repo = target_repo(org:)
 body = "# #{title}\n"
 body += "\nTarget repos:\n<!-- comma-separated owner/repo list — declares scope; /split routes sub-issues within it -->\n" if org
 issue = @issues.create(owner_repo, title: title, body: Plan.to_issue_body(body))
 path = write_linked_plan(owner_repo, issue, body)
 out.puts "dev: created #{owner_repo}##{issue.number} (#{issue.html_url})"
Expand Down

23 changes: 23 additions & 0 deletions
share/cursor-skills/ai-flow/SKILL.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -27,6 +27,29 @@ conflict guard so local content can never clobber newer remote edits.
| "address the open feedback on this plan" | see below |
| org-wide / cross-repo plan (not tied to this repo) | add `--org` to `new`/`link`/`pull` — targets the configured org plans repo |

## Multi-repo plans: the `Target repos:` line

When canonizing a plan whose work lands in other repos (especially
`dev plan link --org`), include a `Target repos: owner/a, owner/b` line near
the top of the plan body. It declares the plan's scope and narrows the repo
menu `/split` routes sub-issues within (`dev plan new --org` scaffolds the
line; fill it in). Without it, `/split` may route to any repo of the org.

## Remote lifecycle (the GitHub-side commands)

Once canonical, the plan is driven from GitHub comments — `/ask` and `/edit`
refine the body, `/split --dry` stages an editable `## Subtasks` yaml
section in the plan body (review/edit it, then `/split --apply`; bare
`/split` does both), `/build` builds a PR (or iterates when commented on a
PR), `/build --split` orchestrates the sub-issues in dependency waves. A
staged (unapplied) `## Subtasks` spec blocks `/build` until applied or
deleted; the section round-trips through `dev plan pull`/`push` like any
other body content. Full reference:
[docs/commands.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/commands.md)
and
[docs/plan-lifecycle.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/plan-lifecycle.md)
in d3mlabs/ai-flow.

## Addressing open feedback

Open feedback lives as issue comments (often quote-anchored). To address it:
Expand Down

6 changes: 4 additions & 2 deletions
test/dev/plan/accessor_test.rb

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -115,10 +115,12 @@ def read_plan(root, name)
 When "creating an org-wide plan"
 accessor.run(["new", "Org roadmap", "--org"], out: StringIO.new)

 Then "the issue lands in the plans repo and the filename disambiguates"
 Then "the issue lands in the plans repo, scaffolded with a Target repos line, and the filename disambiguates"
 issues.get("d3mlabs/plans", 1).title == "Org roadmap"
 header, _body = read_plan(root, "gh-plans-1-org-roadmap.plan.md")
 issues.get("d3mlabs/plans", 1).body.include?("Target repos:")
 header, body = read_plan(root, "gh-plans-1-org-roadmap.plan.md")
 header.owner_repo == "d3mlabs/plans"
 body.include?("Target repos:")

 Cleanup
 FileUtils.rm_rf(dir)
Expand Down
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle by JPDuchesne · Pull Request #39 · d3mlabs/dev · GitHub
Skip to content
Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle#39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

JPDuchesne
merged 1 commit into

from

Jul 18, 2026
 Merged


Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle
#39
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


2 changes: 1 addition & 1 deletion
README.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -291,7 +291,7 @@ Custom integrations implement `Dev::Deps::Integration` (with `install_all(pins,
- **`dev cred get <namespace> <key>`** — resolve a credential through the provider chain (ENV → keychain → file → prompt) and print it. A non-interactive miss errors with `gh secret set` guidance. Mirrors `dev deps path` for shell consumers (e.g. a staging sync).
- **`dev cache gc [--keep N]`** — reclaim host caches dev owns (see below).
- **`dev reset-container`** — remove the persistent build container (clears its incremental cache); registered only when `build.container.persist` is set.
- **`dev plan …`** — sync Cursor plans with GitHub issues (ai-flow): the issue is the canonical plan, the local `.cursor/plans/gh-<n>-<slug>.plan.md` is a transient working copy carrying an `<!-- ai-flow … -->` header. Subcommands: `new "<title>" [--org]` (create issue + linked plan), `link <n> [<file>]` / `link <file>` (attach a draft to an existing issue / create one from it), `pull <n> [--merge]` (fetch, 3-way merging when both sides changed — the merge base lives at `~/.local/state/ai-flow/`), `push [<file>]` (guarded body PATCH — refuses to clobber newer remote edits), and `status` (clean / ahead / behind / diverged, per linked plan). `--org` targets the org plans repo (`plans_repo:` in `~/.config/dev/config.yml`, or `DEV_PLANS_REPO`) instead of the current repo's origin. Every invocation also ensures `~/.cursor/skills/ai-flow` symlinks to the skill shipped in `share/cursor-skills/`, so the Cursor agent knows these verbs. For auto-push, a participating repo adds a Cursor `afterFileEdit` hook to `.cursor/hooks.json` running `dev plan hook-after-edit` — it reads the hook payload from stdin and no-ops unless the edited file is a linked plan.
- **`dev plan …`** — sync Cursor plans with GitHub issues (ai-flow): the issue is the canonical plan, the local `.cursor/plans/gh-<n>-<slug>.plan.md` is a transient working copy carrying an `<!-- ai-flow … -->` header. Subcommands: `new "<title>" [--org]` (create issue + linked plan; `--org` scaffolds a `Target repos:` line), `link <n> [<file>]` / `link <file>` (attach a draft to an existing issue / create one from it), `pull <n> [--merge]` (fetch, 3-way merging when both sides changed — the merge base lives at `~/.local/state/ai-flow/`), `push [<file>]` (guarded body PATCH — refuses to clobber newer remote edits), and `status` (clean / ahead / behind / diverged, per linked plan). `--org` targets the org plans repo (`plans_repo:` in `~/.config/dev/config.yml`, or `DEV_PLANS_REPO`) instead of the current repo's origin. Every invocation also ensures `~/.cursor/skills/ai-flow` symlinks to the skill shipped in `share/cursor-skills/`, so the Cursor agent knows these verbs. For auto-push, a participating repo adds a Cursor `afterFileEdit` hook to `.cursor/hooks.json` running `dev plan hook-after-edit` — it reads the hook payload from stdin and no-ops unless the edited file is a linked plan. What happens to a plan after it's canonical — `/ask`, `/edit`, `/split` (two-phase dry/apply), `/build` — is ai-flow's remote half: see [plan-lifecycle.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/plan-lifecycle.md) and [commands.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/commands.md).

## Build container & caching model

Expand Down

5 changes: 5 additions & 0 deletions
lib/dev/plan/accessor.rb

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -67,13 +67,18 @@ def run(args, out: $stdout, input: $stdin)

 # `dev plan new "<title>" [--org]` — create the issue first (it is
 # canonical from birth), then materialize the linked local working copy.
 # Org plans are scaffolded with a `Target repos:` line: they usually
 # span repos, and the line narrows /split's routing menu (see ai-flow's
 # docs/plan-lifecycle.md). Left blank it is inert — the menu falls back
 # to every org repo.
 def new_plan(args, out:)
 org = args.delete("--org") ? true : false
 title = args.shift
 raise UsageError, "usage: dev plan new \"<title>\" [--org]" if title.nil? || title.empty? || !args.empty?

 owner_repo = target_repo(org:)
 body = "# #{title}\n"
 body += "\nTarget repos:\n<!-- comma-separated owner/repo list — declares scope; /split routes sub-issues within it -->\n" if org
 issue = @issues.create(owner_repo, title: title, body: Plan.to_issue_body(body))
 path = write_linked_plan(owner_repo, issue, body)
 out.puts "dev: created #{owner_repo}##{issue.number} (#{issue.html_url})"
Expand Down

23 changes: 23 additions & 0 deletions
share/cursor-skills/ai-flow/SKILL.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -27,6 +27,29 @@ conflict guard so local content can never clobber newer remote edits.
| "address the open feedback on this plan" | see below |
| org-wide / cross-repo plan (not tied to this repo) | add `--org` to `new`/`link`/`pull` — targets the configured org plans repo |

## Multi-repo plans: the `Target repos:` line

When canonizing a plan whose work lands in other repos (especially
`dev plan link --org`), include a `Target repos: owner/a, owner/b` line near
the top of the plan body. It declares the plan's scope and narrows the repo
menu `/split` routes sub-issues within (`dev plan new --org` scaffolds the
line; fill it in). Without it, `/split` may route to any repo of the org.

## Remote lifecycle (the GitHub-side commands)

Once canonical, the plan is driven from GitHub comments — `/ask` and `/edit`
refine the body, `/split --dry` stages an editable `## Subtasks` yaml
section in the plan body (review/edit it, then `/split --apply`; bare
`/split` does both), `/build` builds a PR (or iterates when commented on a
PR), `/build --split` orchestrates the sub-issues in dependency waves. A
staged (unapplied) `## Subtasks` spec blocks `/build` until applied or
deleted; the section round-trips through `dev plan pull`/`push` like any
other body content. Full reference:
[docs/commands.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/commands.md)
and
[docs/plan-lifecycle.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/plan-lifecycle.md)
in d3mlabs/ai-flow.

## Addressing open feedback

Open feedback lives as issue comments (often quote-anchored). To address it:
Expand Down

6 changes: 4 additions & 2 deletions
test/dev/plan/accessor_test.rb

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -115,10 +115,12 @@ def read_plan(root, name)
 When "creating an org-wide plan"
 accessor.run(["new", "Org roadmap", "--org"], out: StringIO.new)

 Then "the issue lands in the plans repo and the filename disambiguates"
 Then "the issue lands in the plans repo, scaffolded with a Target repos line, and the filename disambiguates"
 issues.get("d3mlabs/plans", 1).title == "Org roadmap"
 header, _body = read_plan(root, "gh-plans-1-org-roadmap.plan.md")
 issues.get("d3mlabs/plans", 1).body.include?("Target repos:")
 header, body = read_plan(root, "gh-plans-1-org-roadmap.plan.md")
 header.owner_repo == "d3mlabs/plans"
 body.include?("Target repos:")

 Cleanup
 FileUtils.rm_rf(dir)
Expand Down
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();
Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle by JPDuchesne · Pull Request #39 · d3mlabs/dev · GitHub
Skip to content
Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle#39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

JPDuchesne
merged 1 commit into

from

Jul 18, 2026
 Merged


Scaffold Target repos: in dev plan new --org; skill covers the remote lifecycle
#39
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


2 changes: 1 addition & 1 deletion
README.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -291,7 +291,7 @@ Custom integrations implement `Dev::Deps::Integration` (with `install_all(pins,
- **`dev cred get <namespace> <key>`** — resolve a credential through the provider chain (ENV → keychain → file → prompt) and print it. A non-interactive miss errors with `gh secret set` guidance. Mirrors `dev deps path` for shell consumers (e.g. a staging sync).
- **`dev cache gc [--keep N]`** — reclaim host caches dev owns (see below).
- **`dev reset-container`** — remove the persistent build container (clears its incremental cache); registered only when `build.container.persist` is set.
- **`dev plan …`** — sync Cursor plans with GitHub issues (ai-flow): the issue is the canonical plan, the local `.cursor/plans/gh-<n>-<slug>.plan.md` is a transient working copy carrying an `<!-- ai-flow … -->` header. Subcommands: `new "<title>" [--org]` (create issue + linked plan), `link <n> [<file>]` / `link <file>` (attach a draft to an existing issue / create one from it), `pull <n> [--merge]` (fetch, 3-way merging when both sides changed — the merge base lives at `~/.local/state/ai-flow/`), `push [<file>]` (guarded body PATCH — refuses to clobber newer remote edits), and `status` (clean / ahead / behind / diverged, per linked plan). `--org` targets the org plans repo (`plans_repo:` in `~/.config/dev/config.yml`, or `DEV_PLANS_REPO`) instead of the current repo's origin. Every invocation also ensures `~/.cursor/skills/ai-flow` symlinks to the skill shipped in `share/cursor-skills/`, so the Cursor agent knows these verbs. For auto-push, a participating repo adds a Cursor `afterFileEdit` hook to `.cursor/hooks.json` running `dev plan hook-after-edit` — it reads the hook payload from stdin and no-ops unless the edited file is a linked plan.
- **`dev plan …`** — sync Cursor plans with GitHub issues (ai-flow): the issue is the canonical plan, the local `.cursor/plans/gh-<n>-<slug>.plan.md` is a transient working copy carrying an `<!-- ai-flow … -->` header. Subcommands: `new "<title>" [--org]` (create issue + linked plan; `--org` scaffolds a `Target repos:` line), `link <n> [<file>]` / `link <file>` (attach a draft to an existing issue / create one from it), `pull <n> [--merge]` (fetch, 3-way merging when both sides changed — the merge base lives at `~/.local/state/ai-flow/`), `push [<file>]` (guarded body PATCH — refuses to clobber newer remote edits), and `status` (clean / ahead / behind / diverged, per linked plan). `--org` targets the org plans repo (`plans_repo:` in `~/.config/dev/config.yml`, or `DEV_PLANS_REPO`) instead of the current repo's origin. Every invocation also ensures `~/.cursor/skills/ai-flow` symlinks to the skill shipped in `share/cursor-skills/`, so the Cursor agent knows these verbs. For auto-push, a participating repo adds a Cursor `afterFileEdit` hook to `.cursor/hooks.json` running `dev plan hook-after-edit` — it reads the hook payload from stdin and no-ops unless the edited file is a linked plan. What happens to a plan after it's canonical — `/ask`, `/edit`, `/split` (two-phase dry/apply), `/build` — is ai-flow's remote half: see [plan-lifecycle.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/plan-lifecycle.md) and [commands.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/commands.md).

## Build container & caching model

Expand Down

5 changes: 5 additions & 0 deletions
lib/dev/plan/accessor.rb

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -67,13 +67,18 @@ def run(args, out: $stdout, input: $stdin)

 # `dev plan new "<title>" [--org]` — create the issue first (it is
 # canonical from birth), then materialize the linked local working copy.
 # Org plans are scaffolded with a `Target repos:` line: they usually
 # span repos, and the line narrows /split's routing menu (see ai-flow's
 # docs/plan-lifecycle.md). Left blank it is inert — the menu falls back
 # to every org repo.
 def new_plan(args, out:)
 org = args.delete("--org") ? true : false
 title = args.shift
 raise UsageError, "usage: dev plan new \"<title>\" [--org]" if title.nil? || title.empty? || !args.empty?

 owner_repo = target_repo(org:)
 body = "# #{title}\n"
 body += "\nTarget repos:\n<!-- comma-separated owner/repo list — declares scope; /split routes sub-issues within it -->\n" if org
 issue = @issues.create(owner_repo, title: title, body: Plan.to_issue_body(body))
 path = write_linked_plan(owner_repo, issue, body)
 out.puts "dev: created #{owner_repo}##{issue.number} (#{issue.html_url})"
Expand Down

23 changes: 23 additions & 0 deletions
share/cursor-skills/ai-flow/SKILL.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -27,6 +27,29 @@ conflict guard so local content can never clobber newer remote edits.
| "address the open feedback on this plan" | see below |
| org-wide / cross-repo plan (not tied to this repo) | add `--org` to `new`/`link`/`pull` — targets the configured org plans repo |

## Multi-repo plans: the `Target repos:` line

When canonizing a plan whose work lands in other repos (especially
`dev plan link --org`), include a `Target repos: owner/a, owner/b` line near
the top of the plan body. It declares the plan's scope and narrows the repo
menu `/split` routes sub-issues within (`dev plan new --org` scaffolds the
line; fill it in). Without it, `/split` may route to any repo of the org.

## Remote lifecycle (the GitHub-side commands)

Once canonical, the plan is driven from GitHub comments — `/ask` and `/edit`
refine the body, `/split --dry` stages an editable `## Subtasks` yaml
section in the plan body (review/edit it, then `/split --apply`; bare
`/split` does both), `/build` builds a PR (or iterates when commented on a
PR), `/build --split` orchestrates the sub-issues in dependency waves. A
staged (unapplied) `## Subtasks` spec blocks `/build` until applied or
deleted; the section round-trips through `dev plan pull`/`push` like any
other body content. Full reference:
[docs/commands.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/commands.md)
and
[docs/plan-lifecycle.md](https://github.com/d3mlabs/ai-flow/blob/HEAD/docs/plan-lifecycle.md)
in d3mlabs/ai-flow.

## Addressing open feedback

Open feedback lives as issue comments (often quote-anchored). To address it:
Expand Down

6 changes: 4 additions & 2 deletions
test/dev/plan/accessor_test.rb

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -115,10 +115,12 @@ def read_plan(root, name)
 When "creating an org-wide plan"
 accessor.run(["new", "Org roadmap", "--org"], out: StringIO.new)

 Then "the issue lands in the plans repo and the filename disambiguates"
 Then "the issue lands in the plans repo, scaffolded with a Target repos line, and the filename disambiguates"
 issues.get("d3mlabs/plans", 1).title == "Org roadmap"
 header, _body = read_plan(root, "gh-plans-1-org-roadmap.plan.md")
 issues.get("d3mlabs/plans", 1).body.include?("Target repos:")
 header, body = read_plan(root, "gh-plans-1-org-roadmap.plan.md")
 header.owner_repo == "d3mlabs/plans"
 body.include?("Target repos:")

 Cleanup
 FileUtils.rm_rf(dir)
Expand Down
Loading