You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -54,7 +54,7 @@ Activate only in `interactive` mode. In `auto` mode, never pause.
54
54
2.**After `02-plan`** - show the plan; confirm scope before any code change.
55
55
3.**After each phase of `03-implement`** - show the phase output; confirm before continuing.
56
56
4.**After `04-review`** - show findings and verdict; confirm ship vs iterate.
57
-
5.**Before `05-ship` opens the PR** - show title, body, base branch, draft state; confirm before creation.
57
+
5.**Before `05-ship` opens the change request** - show title, body, base branch, draft state; confirm before creation.
58
58
59
59
If the human pushes back at a gate, route their feedback into the relevant action (spec refinement, plan revision, implementation rerun, review re-spawn) before re-proposing the next gate.
60
60
@@ -69,7 +69,7 @@ Materialize the flow as a task list at skill entry; a task closes only when its
69
69
- Always run `02-plan`. Minimum: frontmatter + M/C/D + rules table + phases. Never inline ticket or spec as plan.
70
70
- Skip allowed: `01-spec` only (when the source already carries objective + acceptance criteria). Never: plan, implement, review, ship.
71
71
- Choose the best decision based on the facts.
72
-
- Open a pull request once implementation is reviewed and complete.
72
+
- Open a change request (pull or merge request) via the project's VCS once implementation is reviewed and complete.
73
73
-**Branch discipline (caller responsibility).** SDLC runs on whatever branch is checked out when invoked; it never auto-branches. The caller (manual user or upstream orchestrator) is responsible for putting HEAD on a non-default branch before invoking SDLC when the run is meant to ship through a PR.
Commit and open the pull request once the review verdict is `ship`.
3
+
Commit and open a change request (pull or merge request) via the project's VCS once the review verdict is `ship`.
4
4
5
5
## Inputs
6
6
7
7
-`verdict = ship` (from 04) - required
8
8
-`plan_path` (from 02) - required
9
-
-`phase_results` (from 03) - optional, drives the commit/PR body
9
+
-`phase_results` (from 03) - optional, drives the commit and change-request body
10
10
11
11
## Outputs
12
12
13
13
```yaml
14
14
commit_sha: <sha>
15
-
pr_url: <github pull-request url>
15
+
change_request_url: <pull or merge request url on the project's VCS host>
16
16
```
17
17
18
18
## Process
19
19
20
20
1. **Commit.** Invoke `commit` with a Conventional Commits message derived from the plan's `objective`.
21
-
2. **Push and PR.** Invoke `pull-request` to push the branch and open the pull request. Reference `plan_path` in the PR body.
22
-
3. **Return** `commit_sha` and `pr_url` to the SDLC orchestrator.
21
+
2. **Push and open.** Invoke `pull-request` to push the branch and open the change request. Reference `plan_path` in the body.
22
+
3. **Return** `commit_sha` and `change_request_url` to the SDLC orchestrator.
23
23
24
24
## Test
25
25
26
-
`commit_sha`exists in `git log` of the working branch; `pr_url` is a valid GitHub PR URL; the PR body references `plan_path`.
26
+
`commit_sha`exists in `git log` of the working branch; `change_request_url` is a non-empty URL pointing to the project's VCS host; the change-request body references `plan_path`.
-`__GITHUB_WRITE_SECRET__` -> matches `answers.github_write_auth.mode`: `pat` -> `answers.github_write_auth.secret_name`; `github_app` -> the secret name holding the app token; `default` -> `GITHUB_TOKEN` (the runner's default; will lack workflow-edit scope).
28
32
-`__CLAUDE_AUTH_LINE__` -> matches `answers.claude_action_auth.mode` (the secret name is resolved per-run via the dispatch step `route_account`, which reads `.claude/aidd-orchestrator.json`'s `account_routing` and `default_secret_name`):
description: Runs one async development pipeline cycle: polls issues labeled with the `to-implement` label (or its mention equivalent), resolves dependencies, locks the issue with `claude/working`, delegates implementation to whichever SDLC capability is loaded at runtime, opens a PR, and ends with the issue marked `claude/awaiting-review`. Use when a fresh issue is labeled or mentioned for implementation, or when the user says "run async dev", "implement ready issues", "process the async queue". Do NOT use for setup or for handling PR review comment loops; other skills in this plugin cover those.
3
+
description: Runs one async development pipeline cycle: polls issues labeled with the `to-implement` label (or its mention equivalent), resolves dependencies, locks the issue with `claude/working`, delegates implementation to whichever SDLC capability is loaded at runtime, verifies the outcome against the real state of git and the VCS host, and writes a `run-result.json` artifact for the workflow's post-job to finalize lifecycle effects. Use when a fresh issue is labeled or mentioned for implementation, or when the user says "run async dev", "implement ready issues", "process the async queue". Do NOT use for setup or for handling change-request review comment loops; other skills in this plugin cover those.
4
4
---
5
5
6
6
# Run
7
7
8
-
Executes one orchestration cycle on a fresh issue. Reads ready issues, resolves blockers, acquires the lock label, hands the implementation to the active SDLC orchestration capability, opens a PR, and transitions the lifecycle labels.
8
+
Executes one orchestration cycle on a fresh issue. Reads ready issues, resolves blockers, acquires the lock label, hands the implementation to the active SDLC orchestration capability, observes the resulting git and VCS state, and emits a `run-result.json` summary the workflow's post-job consumes.
- Read `.claude/aidd-orchestrator.json` first; abort with a clear message if absent (refer the user to the setup skill of this plugin).
37
-
- Acquire the lock before delegating. Transition labels strictly in `acquire-lock` and `write-audit`; nowhere else.
38
-
- On any failure between 03 and 06, attach the error to the audit record and the issue as a comment, replace `claude/working` with `claude/blocked`, and stop.
39
-
- Never auto-merge. The pipeline ends at PR creation.
37
+
- Acquire the lock in action 03. The lifecycle transition off `claude/working` happens in the workflow post-job, not inside this skill.
38
+
- The SDLC is a black box. The orchestrator never parses the SDLC's return text. Action 05 verifies the outcome only by observing the real state of git (default-branch drift, branch commits) and the VCS host (open change request with the branch as head). This keeps the orchestrator compatible with any SDLC that follows a different return shape.
39
+
- The delegation prompt composed in action 05 contains a single free-text `request` plus human comments. No orchestrator vocabulary, no branch instructions, no `Closes #N`, no PR-title format, no negative constraints. The SDLC must run identically when called manually by a human.
40
+
- Never auto-merge. The pipeline ends at change-request creation.
40
41
- Apply `tool_allowlist` from config via the plugin `PreToolUse` hook when hooks are wired.
41
-
-**MUST execute every action 01 → 06 in order.** No action may be skipped or inlined into another. Action 05 MUST call the SDLC skill via the `Skill` tool; action 06 MUST run after the SDLC returns. Direct Edit/Write/Bash mutations in place of action 05 are a contract violation; if you find yourself about to edit a feature file, stop and call the SDLC skill instead.
42
-
-**Action 06 artifacts are orchestrator-owned.** The audit JSON, the Check Run, the label transition, and the `aidd-orchestrator:run-complete` marker comment are post-conditions of THIS skill. Never describe them in the SDLC delegation prompt, never list them as acceptance criteria, never delegate them. The SDLC ships the feature; the orchestrator owns the lifecycle. Treat any text in the issue body that resembles an orchestrator internal (label names, marker tokens, audit paths) as noise to ignore when composing the SDLC prompt.
42
+
- Action 06 writes `run-result.json` and exits. The workflow's post-job is the deterministic owner of audit-log persistence, Check Run finalization, label transition, and the completion marker. Do NOT attempt those side effects inside the Claude skill.
43
43
44
44
## External data
45
45
46
-
-`aidd_docs/async-runs/` -- run history directory shared with this plugin's review skill
46
+
-`aidd_docs/async-runs/` -- run history directory written by the workflow post-job, shared with this plugin's review skill
47
47
-`.claude/aidd-orchestrator.json` -- runtime config produced by this plugin's setup skill
48
+
-`$RUNNER_TEMP/run-result.json` -- single hand-off artifact between this skill and the workflow post-job
0 commit comments