@aiaiai-pt/manda-cli 0.1.1 → 0.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/commands.d.ts +1 -1
- package/dist/commands.js +4 -1
- package/package.json +1 -1
package/dist/commands.d.ts
CHANGED
|
@@ -5,7 +5,7 @@ export declare function projects(config: Config, flags: Flags): Promise<void>;
|
|
|
5
5
|
export declare function inbox(config: Config, flags: Flags): Promise<void>;
|
|
6
6
|
export declare function next(config: Config, flags: Flags): Promise<void>;
|
|
7
7
|
/** A block for CLAUDE.md or AGENTS.md: the loop a harness runs with manda as its coordination layer. */
|
|
8
|
-
export declare const INSTRUCTIONS = "## Manda: customer feedback and work coordination\n\nManda is the ledger of what customers reported and what they have been told. Use the `manda`\nCLI (`npm i -g @aiaiai-pt/manda-cli`, `MANDA_TOKEN` set) as the coordination layer while\nworking in this codebase, alone or with a person. Every call prints JSON when piped; exit codes:\n0 ok, 1 usage, 2 auth, 3 conflict (reload and decide again), 4 not found, 5 other.\n\nThe loop:\n\n1. `manda next --json` lists open reports you own or nobody owns, in priority order. Take the first.\n2. `manda report show <id> --json` reads the report and its timeline. `manda report assign <id> --to me` takes it\n (owned reports rank first in `next`; an unowned one you are working on will sink below fresh reports), then\n `manda report ack <id>` starts review.\n3. Group it: `manda topic list --json` to find the topic it belongs to, then\n `manda topic link-report <topic> --report <id>`; or `manda topic create --project <project> --title \"<customer intent>\"`\n and `manda topic transition <topic> plan` then `start` when you begin.\n4. Do the work in the repository. Put `Manda-Report: <id>` and `Manda-Topic: <topic>` as commit trailers\n and `manda topic link-work <topic> --tracker github --issue <pr number> --issue-url <pr url>` once a PR exists.\n5. Tell the customer only when it is true
|
|
8
|
+
export declare const INSTRUCTIONS = "## Manda: customer feedback and work coordination\n\nManda is the ledger of what customers reported and what they have been told. Use the `manda`\nCLI (`npm i -g @aiaiai-pt/manda-cli`, `MANDA_TOKEN` set) as the coordination layer while\nworking in this codebase, alone or with a person. Every call prints JSON when piped; exit codes:\n0 ok, 1 usage, 2 auth, 3 conflict (reload and decide again), 4 not found, 5 other.\n\nThe loop:\n\n1. `manda next --json` lists open reports you own or nobody owns, in priority order. Take the first.\n2. `manda report show <id> --json` reads the report and its timeline. `manda report assign <id> --to me` takes it\n (owned reports rank first in `next`; an unowned one you are working on will sink below fresh reports), then\n `manda report ack <id>` starts review.\n3. Group it: `manda topic list --json` to find the topic it belongs to, then\n `manda topic link-report <topic> --report <id>`; or `manda topic create --project <project> --title \"<customer intent>\"`\n and `manda topic transition <topic> plan` then `start` when you begin.\n4. Do the work in the repository. Put `Manda-Report: <id>` and `Manda-Topic: <topic>` as commit trailers\n and `manda topic link-work <topic> --tracker github --issue <pr number> --issue-url <pr url>` once a PR exists.\n5. Tell the customer only when it is true, and \"true\" means you exercised their path, not the artefact:\n load the page or call the entry point they use (the hosted script, the endpoint, the screen) on the\n deployed version and watch it work. A green suite, a merged PR or a file read back are not that.\n Then `manda report comment <id> --audience customer --outcome resolved --body \"<what changed, in their words>\"`.\n Internal notes use `--audience internal`. Never resolve without a customer-facing explanation.\n6. `manda topic transition <topic> complete` when the change is available to customers; `manda topic announce <topic> --body \"<progress>\"` for public progress.\n\nRules: read before you write (every write checks the revision); do not reprioritise by editing reports, reorder topics\n(`manda topic reorder`) with the person who owns the roadmap; a 3 exit means someone else changed it, re-read and decide again.\n";
|
|
9
9
|
export declare function instructions(): void;
|
|
10
10
|
export declare function reportShow(config: Config, id: string, flags: Flags): Promise<void>;
|
|
11
11
|
export declare function reportCapture(config: Config, flags: Flags): Promise<void>;
|
package/dist/commands.js
CHANGED
|
@@ -183,7 +183,10 @@ The loop:
|
|
|
183
183
|
and \`manda topic transition <topic> plan\` then \`start\` when you begin.
|
|
184
184
|
4. Do the work in the repository. Put \`Manda-Report: <id>\` and \`Manda-Topic: <topic>\` as commit trailers
|
|
185
185
|
and \`manda topic link-work <topic> --tracker github --issue <pr number> --issue-url <pr url>\` once a PR exists.
|
|
186
|
-
5. Tell the customer only when it is true
|
|
186
|
+
5. Tell the customer only when it is true, and "true" means you exercised their path, not the artefact:
|
|
187
|
+
load the page or call the entry point they use (the hosted script, the endpoint, the screen) on the
|
|
188
|
+
deployed version and watch it work. A green suite, a merged PR or a file read back are not that.
|
|
189
|
+
Then \`manda report comment <id> --audience customer --outcome resolved --body "<what changed, in their words>"\`.
|
|
187
190
|
Internal notes use \`--audience internal\`. Never resolve without a customer-facing explanation.
|
|
188
191
|
6. \`manda topic transition <topic> complete\` when the change is available to customers; \`manda topic announce <topic> --body "<progress>"\` for public progress.
|
|
189
192
|
|