Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
4 changes: 4 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,10 @@

All notable changes to Context are documented here.

## Unreleased

- The routine update example now starts the scheduled task content with a plain line naming the Context Skill instead of a slash command. Some schedulers expand a leading slash command into the Skill text and drop the rest, so the run never saw its paragraph and `ROUTINE_POLICY` and stopped to ask what to do.

## 0.7.99 - 2026-11-13

- `context task rollback` no longer gets stuck with an unfinished production stage: `context close` and the build accept the active rollback, and the rollback cleanup removes the stage. Previously close stopped with `production-not-complete` and the cleanup could not run.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ instance configuration may also define `ROUTINE_POLICY` defaults; keys in the
trigger take precedence. For example, a scheduler's task content:

```text
/c4a:context routine update
Routine update: use the `c4a:context` Skill and follow its routine update procedure.

This is the routine update of the Billing knowledge base. Refresh it from the
latest registered code and documents, revise the affected articles so they
Expand All @@ -29,7 +29,10 @@ ROUTINE_POLICY:
time_budget_minutes: 90 # stop starting new batches after this
```

Start the trigger with one short paragraph naming the knowledge base and what the
Begin the content with a plain line that names this Skill and the routine
update, not with a slash command: some schedulers expand a leading command into
the Skill text and drop everything after it, so the run never sees its settings.
Then write one short paragraph naming the knowledge base and what the
run should achieve, including any team-specific guidance; it tells the agent
which workspace and what matters. The paragraph may also set the reviews in
plain language: an explicit statement that the whole run is managed and reviewed
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ instance configuration may also define `ROUTINE_POLICY` defaults; keys in the
trigger take precedence. For example, a scheduler's task content:

```text
/c4a:context routine update
Routine update: use the `c4a:context` Skill and follow its routine update procedure.

This is the routine update of the Billing knowledge base. Refresh it from the
latest registered code and documents, revise the affected articles so they
Expand All @@ -29,7 +29,10 @@ ROUTINE_POLICY:
time_budget_minutes: 90 # stop starting new batches after this
```

Start the trigger with one short paragraph naming the knowledge base and what the
Begin the content with a plain line that names this Skill and the routine
update, not with a slash command: some schedulers expand a leading command into
the Skill text and drop everything after it, so the run never sees its settings.
Then write one short paragraph naming the knowledge base and what the
run should achieve, including any team-specific guidance; it tells the agent
which workspace and what matters. The paragraph may also set the reviews in
plain language: an explicit statement that the whole run is managed and reviewed
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ instance configuration may also define `ROUTINE_POLICY` defaults; keys in the
trigger take precedence. For example, a scheduler's task content:

```text
/c4a-context routine update
Routine update: use the `c4a:context` Skill and follow its routine update procedure.

This is the routine update of the Billing knowledge base. Refresh it from the
latest registered code and documents, revise the affected articles so they
Expand All @@ -29,7 +29,10 @@ ROUTINE_POLICY:
time_budget_minutes: 90 # stop starting new batches after this
```

Start the trigger with one short paragraph naming the knowledge base and what the
Begin the content with a plain line that names this Skill and the routine
update, not with a slash command: some schedulers expand a leading command into
the Skill text and drop everything after it, so the run never sees its settings.
Then write one short paragraph naming the knowledge base and what the
run should achieve, including any team-specific guidance; it tells the agent
which workspace and what matters. The paragraph may also set the reviews in
plain language: an explicit statement that the whole run is managed and reviewed
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ instance configuration may also define `ROUTINE_POLICY` defaults; keys in the
trigger take precedence. For example, a scheduler's task content:

```text
/c4a:context routine update
Routine update: use the `c4a:context` Skill and follow its routine update procedure.

This is the routine update of the Billing knowledge base. Refresh it from the
latest registered code and documents, revise the affected articles so they
Expand All @@ -29,7 +29,10 @@ ROUTINE_POLICY:
time_budget_minutes: 90 # stop starting new batches after this
```

Start the trigger with one short paragraph naming the knowledge base and what the
Begin the content with a plain line that names this Skill and the routine
update, not with a slash command: some schedulers expand a leading command into
the Skill text and drop everything after it, so the run never sees its settings.
Then write one short paragraph naming the knowledge base and what the
run should achieve, including any team-specific guidance; it tells the agent
which workspace and what matters. The paragraph may also set the reviews in
plain language: an explicit statement that the whole run is managed and reviewed
Expand Down
7 changes: 5 additions & 2 deletions plugins/context/skills/context/references/routine-update.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ instance configuration may also define `ROUTINE_POLICY` defaults; keys in the
trigger take precedence. For example, a scheduler's task content:

```text
/c4a:context routine update
Routine update: use the `c4a:context` Skill and follow its routine update procedure.

This is the routine update of the Billing knowledge base. Refresh it from the
latest registered code and documents, revise the affected articles so they
Expand All @@ -29,7 +29,10 @@ ROUTINE_POLICY:
time_budget_minutes: 90 # stop starting new batches after this
```

Start the trigger with one short paragraph naming the knowledge base and what the
Begin the content with a plain line that names this Skill and the routine
update, not with a slash command: some schedulers expand a leading command into
the Skill text and drop everything after it, so the run never sees its settings.
Then write one short paragraph naming the knowledge base and what the
run should achieve, including any team-specific guidance; it tells the agent
which workspace and what matters. The paragraph may also set the reviews in
plain language: an explicit statement that the whole run is managed and reviewed
Expand Down
Loading