Skip to content

Describe plan record label as creation state in security/refactor #38

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
DocksDocks merged 1 commit into from
Aug 25, 2026
Merged

Describe plan record label as creation state in security/refactor #38

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
6 changes: 3 additions & 3 deletions plugins/docks/skills/engineering/refactor/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ user-invocable: true
metadata:
pattern: pipeline
updated: "2026-08-25"
content_hash: "082d42dc672fe8b5374559ca3f13585651d9c603288a9705bf4f759f8d897eac"
content_hash: "f71d5e5486566c6703275bafa0a70364dfd7fb3d3f9558c5f41950f725a1a2dc"
---

# Refactor (cross-tool pipeline)
Expand Down Expand Up @@ -74,8 +74,8 @@ Phase 3 uses Phase 2a's SAFE tier to skip files about to be deleted. Phase 4 mer
## The plan record (IPC + deliverable)

```text
GitHub issue #<n> labeled plan plus exactly one lifecycle label:
plan:drafting | plan:planned | plan:ongoing | plan:blocked
GitHub issue #<n> labeled plan, created with plan:drafting;
plan-manager owns every later phase transition.
```

Hand phase output to `plan-manager` as you go — do not hold all of it in context and dump it at the end. Downstream phases and a resumed run read the issue with `plan.mjs show <issue> --body` and locate prior output by grepping the headings.
Expand Down
6 changes: 3 additions & 3 deletions plugins/docks/skills/engineering/security/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ user-invocable: true
metadata:
pattern: pipeline
updated: "2026-08-25"
content_hash: "f108c4f561c1c05d73670783cdc425333b867e6cc64057289d7c85a8d7e290a7"
content_hash: "0bc63235cff0a0e7225217ea04e230e5c80e75bff547c967d92efb0957c7d681"
---

# Security Audit (cross-tool pipeline)
Expand Down Expand Up @@ -75,8 +75,8 @@ Phases 2a–2c are independent lenses over the same Phase 1 map; run them sequen
The plan issue holds the whole run. It doubles as inter-phase memory and the final artifact.

```text
GitHub issue #<n> labeled plan plus exactly one lifecycle label:
plan:drafting | plan:planned | plan:ongoing | plan:blocked
GitHub issue #<n> labeled plan, created with plan:drafting;
plan-manager owns every later phase transition.
```

Hand phase output to `plan-manager` as you go — do not hold all of it in context and dump it at the end. The headings above are the contract; downstream phases and a resumed run read the issue with `plan.mjs show <issue> --body` and locate prior output by grepping for them.
Expand Down