@markjaquith/agency 2.46.0 → 2.47.0

package/README.md

@@ -99,7 +99,11 @@ The OpenCode config defines an `@agency` subagent for delegated workbase
 orchestration, loads Agency's hidden instructions in addition to any user-owned
 root `AGENTS.md`, advertises the complete workbase as one portable reference,
 and replaces the built-in Plan agent with `agency-plan`. That planning agent can
-update `TASK.md`, `PHASE.md`, and `EPIC.md` while other edits remain disabled.
+update `TASK.md`, `PHASE.md`, and `EPIC.md`, inspect the workbase through
+read-only Agency commands, and use explicit Agency CLI permissions to create or
+update planning structure. Its normal research tools and the complete Agency CLI
+remain available; managed Agency instructions and reported authority govern each
+operation.
 When the subagent launches work in another agent, it verifies that the runner
 started and returns without waiting for the task to finish.
 The TUI-only `/agency-debug` command reports TUI companion initialization and

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@markjaquith/agency",
-  "version": "2.46.0",
+  "version": "2.47.0",
   "description": "Manage agentic work across repositories with durable workbases",
   "keywords": [
     "agents",

package/src/commands/init.test.ts

@@ -49,6 +49,9 @@ describe("init command", () => {
 		expect(config.agent["agency-plan"]).toMatchObject({
 			mode: "primary",
 			permission: {
+				bash: {
+					"agency *": "allow",
+				},
 				edit: {
 					"*": "deny",
 					"tasks/*/TASK.md": "allow",

package/src/services/IntegrationService.test.ts

@@ -283,11 +283,14 @@ describe("IntegrationService", () => {
 			},
 			"agency-plan": {
 				description:
-					"Agency planning mode. May edit only Agency planning documents.",
+					"Agency planning mode. May update Agency plans and planning structure.",
 				mode: "primary",
 				prompt: expect.stringContaining("You are in Agency Plan mode"),
 				permission: {
 					question: "allow",
+					bash: {
+						"agency *": "allow",
+					},
 					edit: {
 						"*": "deny",
 						"tasks/*/TASK.md": "allow",
@@ -307,6 +310,23 @@ describe("IntegrationService", () => {
 		expect(config.agent.agency.prompt).toContain(
 			"return without waiting for the task to finish",
 		)
+		expect(config.agent["agency-plan"].prompt).toContain(
+			"Start with `agency context . --json`",
+		)
+		expect(config.agent["agency-plan"].prompt).toContain(
+			"decompose it into independently deliverable tasks",
+		)
+		expect(config.agent["agency-plan"].prompt).toContain("Use `--if-revision`")
+		expect(config.agent["agency-plan"].prompt).toContain(
+			"available ticket tools",
+		)
+		expect(config.agent["agency-plan"].prompt).toContain(
+			"changing lifecycle state",
+		)
+		expect(config.agent["agency-plan"].prompt).toContain(
+			"Follow the managed Agency instructions and reported authority",
+		)
+		expect(config.agent["agency-plan"].permission.bash["*"]).toBeUndefined()
 		expect(config.references).toEqual({
 			workbase: {
 				path: "..",

package/src/workbase/opencode-file.ts

@@ -8,7 +8,17 @@ const checksum = (content: string) =>
 
 const agencyPlanPrompt = `You are in Agency Plan mode. Think, read, search, and delegate exploration to construct a well-formed plan for the user's goal. Keep the plan comprehensive but concise, and ask clarifying questions when important tradeoffs or intent are unclear.
 
-You may edit TASK.md, PHASE.md, and EPIC.md to record the outcome, current approach, and important decisions. Do not edit any other file or use shell commands to modify the system.`
+Start with \`agency context . --json\`. Use its document paths and revisions, then inspect the graph, related epics, tasks, phases, linked tickets, and repository declarations needed to understand the work. Use machine-readable Agency output when available instead of inferring structure from directory names.
+
+When planning an epic, decompose it into independently deliverable tasks with explicit dependencies. Add phases only when one task genuinely requires multiple ordered delivery units. Reuse or update existing work instead of creating duplicate tasks or phases.
+
+Use the Agency CLI for full workbase orchestration when the plan requires it, including creating or updating related epics, tasks, and phases; moving tasks; maintaining dependencies; and changing lifecycle state. Use \`--if-revision\` with the revision returned by context for mutations that support it, and run \`agency validate\` after changing workbase structure. Use available ticket tools to inspect or update a linked external ticket when the plan requires it.
+
+You may edit TASK.md, PHASE.md, and EPIC.md to record the outcome, current approach, and important decisions. Do not edit any other file or use shell commands to modify the system. Follow the managed Agency instructions and reported authority for every Agency operation.`
+
+const agencyPlanBashPermissions = {
+	"agency *": "allow",
+}
 
 const body = () =>
 	`${JSON.stringify(
@@ -28,11 +38,12 @@ const body = () =>
 				},
 				"agency-plan": {
 					description:
-						"Agency planning mode. May edit only Agency planning documents.",
+						"Agency planning mode. May update Agency plans and planning structure.",
 					mode: "primary",
 					prompt: agencyPlanPrompt,
 					permission: {
 						question: "allow",
+						bash: agencyPlanBashPermissions,
 						edit: {
 							"*": "deny",
 							"tasks/*/TASK.md": "allow",