Skip to content

Commit cbae631

Browse files
bigboatengbigboateng
authored
Fix delivery resolution and operation skill discovery (#187)
1 parent cc8b10f commit cbae631

33 files changed

Lines changed: 1005 additions & 175 deletions

File tree

‎.agents/skills/boatstack-autoplan/SKILL.md‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
name: boatstack-autoplan
3+
description: Create and approve a verified delivery plan. Use only when the user explicitly selects this Boatstack operation.
4+
---
5+
6+
# Boatstack Autoplan
7+
8+
Select the `approved-plan` terminal. This trigger supplies planning intent only. It never approves unseen plan bytes.
9+
10+
Run `boatstack status --repo . --format json` once for observation. An authority-free
11+
`FRONTIER` from status is diagnostic only and cannot terminate this selected operation.
12+
13+
Bind one command-scoped context containing the exact goal, delivery, repository,
14+
worktree, flow, actor, and supplied authority receipts. Preserve that context
15+
through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
16+
authority or infer it from authentication, files, branches, or prior conversation.
17+
18+
Begin each cycle with an untargeted authority-bearing `next`. Apply only the
19+
stable transition ID from the immediately preceding prescription and only its
20+
declared parameters. Preserve the complete apply response and stderr, including
21+
admission, receipt, postcondition, error, recovery, and transaction fields.
22+
Re-resolve with the same context after every complete receipt.
23+
24+
Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
25+
`UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
26+
If recovery is active, use only a transition in `recovery_info.permitted` and
27+
the exact transaction ID. Never choose maintenance, correction, abandonment,
28+
merge, provider, or destructive authority as an escape from a frontier.

‎.agents/skills/boatstack-autoplan/agents/openai.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
interface:
2+
display_name: "Boatstack Autoplan"
3+
short_description: "Create and approve a verified delivery plan."
4+
default_prompt: "Use $boatstack-autoplan to follow the authority-preserving Boatstack V2 driver."
5+
policy:
6+
allow_implicit_invocation: false

‎.agents/skills/boatstack-run/SKILL.md‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
name: boatstack-run
3+
description: Drive delivery to an open or updated pull request. Use only when the user explicitly selects this Boatstack operation.
4+
---
5+
6+
# Boatstack Run
7+
8+
Select the `open-or-updated-pr` terminal. This trigger never grants merge authority. Provider authority remains a separate verified receipt.
9+
10+
Run `boatstack status --repo . --format json` once for observation. An authority-free
11+
`FRONTIER` from status is diagnostic only and cannot terminate this selected operation.
12+
13+
Bind one command-scoped context containing the exact goal, delivery, repository,
14+
worktree, flow, actor, and supplied authority receipts. Preserve that context
15+
through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
16+
authority or infer it from authentication, files, branches, or prior conversation.
17+
18+
Begin each cycle with an untargeted authority-bearing `next`. Apply only the
19+
stable transition ID from the immediately preceding prescription and only its
20+
declared parameters. Preserve the complete apply response and stderr, including
21+
admission, receipt, postcondition, error, recovery, and transaction fields.
22+
Re-resolve with the same context after every complete receipt.
23+
24+
Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
25+
`UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
26+
If recovery is active, use only a transition in `recovery_info.permitted` and
27+
the exact transaction ID. Never choose maintenance, correction, abandonment,
28+
merge, provider, or destructive authority as an escape from a frontier.

‎.agents/skills/boatstack-run/agents/openai.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
interface:
2+
display_name: "Boatstack Run"
3+
short_description: "Drive delivery to an open or updated pull request."
4+
default_prompt: "Use $boatstack-run to follow the authority-preserving Boatstack V2 driver."
5+
policy:
6+
allow_implicit_invocation: false

‎.agents/skills/boatstack-update/SKILL.md‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
name: boatstack-update
3+
description: Apply a checksum-verified Boatstack update. Use only when the user explicitly selects this Boatstack operation.
4+
---
5+
6+
# Boatstack Update
7+
8+
Select the `installation.update` transition. This trigger does not reclassify or advance a product delivery.
9+
10+
Run `boatstack status --repo . --format json` once for observation. An authority-free
11+
`FRONTIER` from status is diagnostic only and cannot terminate this selected operation.
12+
13+
Bind one command-scoped context containing the exact goal, delivery, repository,
14+
worktree, flow, actor, and supplied authority receipts. Preserve that context
15+
through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
16+
authority or infer it from authentication, files, branches, or prior conversation.
17+
18+
Begin each cycle with an untargeted authority-bearing `next`. Apply only the
19+
stable transition ID from the immediately preceding prescription and only its
20+
declared parameters. Preserve the complete apply response and stderr, including
21+
admission, receipt, postcondition, error, recovery, and transaction fields.
22+
Re-resolve with the same context after every complete receipt.
23+
24+
Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
25+
`UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
26+
If recovery is active, use only a transition in `recovery_info.permitted` and
27+
the exact transaction ID. Never choose maintenance, correction, abandonment,
28+
merge, provider, or destructive authority as an escape from a frontier.

‎.agents/skills/boatstack-update/agents/openai.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
interface:
2+
display_name: "Boatstack Update"
3+
short_description: "Apply a checksum-verified Boatstack update."
4+
default_prompt: "Use $boatstack-update to follow the authority-preserving Boatstack V2 driver."
5+
policy:
6+
allow_implicit_invocation: false

‎.claude/skills/boatstack-autoplan/SKILL.md‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
name: boatstack-autoplan
3+
description: Create and approve a verified delivery plan. Use only when the user explicitly selects this Boatstack operation.
4+
---
5+
6+
# Boatstack Autoplan
7+
8+
Select the `approved-plan` terminal. This trigger supplies planning intent only. It never approves unseen plan bytes.
9+
10+
Run `boatstack status --repo . --format json` once for observation. An authority-free
11+
`FRONTIER` from status is diagnostic only and cannot terminate this selected operation.
12+
13+
Bind one command-scoped context containing the exact goal, delivery, repository,
14+
worktree, flow, actor, and supplied authority receipts. Preserve that context
15+
through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
16+
authority or infer it from authentication, files, branches, or prior conversation.
17+
18+
Begin each cycle with an untargeted authority-bearing `next`. Apply only the
19+
stable transition ID from the immediately preceding prescription and only its
20+
declared parameters. Preserve the complete apply response and stderr, including
21+
admission, receipt, postcondition, error, recovery, and transaction fields.
22+
Re-resolve with the same context after every complete receipt.
23+
24+
Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
25+
`UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
26+
If recovery is active, use only a transition in `recovery_info.permitted` and
27+
the exact transaction ID. Never choose maintenance, correction, abandonment,
28+
merge, provider, or destructive authority as an escape from a frontier.

‎.claude/skills/boatstack-run/SKILL.md‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
name: boatstack-run
3+
description: Drive delivery to an open or updated pull request. Use only when the user explicitly selects this Boatstack operation.
4+
---
5+
6+
# Boatstack Run
7+
8+
Select the `open-or-updated-pr` terminal. This trigger never grants merge authority. Provider authority remains a separate verified receipt.
9+
10+
Run `boatstack status --repo . --format json` once for observation. An authority-free
11+
`FRONTIER` from status is diagnostic only and cannot terminate this selected operation.
12+
13+
Bind one command-scoped context containing the exact goal, delivery, repository,
14+
worktree, flow, actor, and supplied authority receipts. Preserve that context
15+
through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
16+
authority or infer it from authentication, files, branches, or prior conversation.
17+
18+
Begin each cycle with an untargeted authority-bearing `next`. Apply only the
19+
stable transition ID from the immediately preceding prescription and only its
20+
declared parameters. Preserve the complete apply response and stderr, including
21+
admission, receipt, postcondition, error, recovery, and transaction fields.
22+
Re-resolve with the same context after every complete receipt.
23+
24+
Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
25+
`UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
26+
If recovery is active, use only a transition in `recovery_info.permitted` and
27+
the exact transaction ID. Never choose maintenance, correction, abandonment,
28+
merge, provider, or destructive authority as an escape from a frontier.

‎.claude/skills/boatstack-update/SKILL.md‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
name: boatstack-update
3+
description: Apply a checksum-verified Boatstack update. Use only when the user explicitly selects this Boatstack operation.
4+
---
5+
6+
# Boatstack Update
7+
8+
Select the `installation.update` transition. This trigger does not reclassify or advance a product delivery.
9+
10+
Run `boatstack status --repo . --format json` once for observation. An authority-free
11+
`FRONTIER` from status is diagnostic only and cannot terminate this selected operation.
12+
13+
Bind one command-scoped context containing the exact goal, delivery, repository,
14+
worktree, flow, actor, and supplied authority receipts. Preserve that context
15+
through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
16+
authority or infer it from authentication, files, branches, or prior conversation.
17+
18+
Begin each cycle with an untargeted authority-bearing `next`. Apply only the
19+
stable transition ID from the immediately preceding prescription and only its
20+
declared parameters. Preserve the complete apply response and stderr, including
21+
admission, receipt, postcondition, error, recovery, and transaction fields.
22+
Re-resolve with the same context after every complete receipt.
23+
24+
Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
25+
`UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
26+
If recovery is active, use only a transition in `recovery_info.permitted` and
27+
the exact transaction ID. Never choose maintenance, correction, abandonment,
28+
merge, provider, or destructive authority as an escape from a frontier.

‎.cursor/commands/boatstack-autoplan.md‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
name: boatstack-autoplan
3+
description: Create and approve a verified delivery plan. Use only when the user explicitly selects this Boatstack operation.
4+
---
5+
6+
# Boatstack Autoplan
7+
8+
Select the `approved-plan` terminal. This trigger supplies planning intent only. It never approves unseen plan bytes.
9+
10+
Run `boatstack status --repo . --format json` once for observation. An authority-free
11+
`FRONTIER` from status is diagnostic only and cannot terminate this selected operation.
12+
13+
Bind one command-scoped context containing the exact goal, delivery, repository,
14+
worktree, flow, actor, and supplied authority receipts. Preserve that context
15+
through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
16+
authority or infer it from authentication, files, branches, or prior conversation.
17+
18+
Begin each cycle with an untargeted authority-bearing `next`. Apply only the
19+
stable transition ID from the immediately preceding prescription and only its
20+
declared parameters. Preserve the complete apply response and stderr, including
21+
admission, receipt, postcondition, error, recovery, and transaction fields.
22+
Re-resolve with the same context after every complete receipt.
23+
24+
Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
25+
`UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
26+
If recovery is active, use only a transition in `recovery_info.permitted` and
27+
the exact transaction ID. Never choose maintenance, correction, abandonment,
28+
merge, provider, or destructive authority as an escape from a frontier.

0 commit comments

Comments
 (0)