/artyfacts
Work with your Artyfacts workspace using artyfacts-pp-cli.
/artyfacts # workspace overview
/artyfacts list my recent specs
/artyfacts create a feature spec for payments
/artyfacts search authentication
/artyfacts sync
/artyfacts show me stale artifacts
Step 1 — always check auth first
artyfacts-pp-cli auth status
If not authenticated:
artyfacts-pp-cli auth login
Step 2 — map intent to command
| User says |
Command group |
| list / browse / show / find |
artifacts list, artifacts tree |
| search / look for |
search-local (or artifacts list --search) |
| create / write / make |
workflow create-with-sections or artifacts create + sections create |
| update / change / rename / move / archive |
artifacts update, sections update |
| delete / remove a section |
sections delete |
| delete an artifact |
no CLI command — use curl -X DELETE $BASE_URL/artifacts/<id> with the Bearer token |
| bulk archive / promote / transition |
artifacts bulk-status — status-only PATCH is not supported by the API; see Known Limitations |
| sync / refresh / pull |
sync |
| stats / insights / who wrote what |
artifacts stats |
| stale / out of date |
artifacts stale |
| org settings / conventions |
org context |
| export / backup |
export |
| import / restore |
import |
| log in / get key / check auth |
auth login, auth status |
Valid artifact types: doc, spec, research, report, experiment, phase, runbook, folder. Do not use document — it is rejected by the API.
Default output flag: use --json whenever you need to parse or display structured data. Use --agent for non-interactive multi-step flows.
No arguments: run artifacts list --json, artifacts stats --json, and org context --json to produce a workspace overview.
Reference files
Load these when you need flag details, enumerations, or step-by-step examples:
- Read references/commands.md — full flag reference for every command
- Read references/global-flags.md — output, behavior, and delivery flags shared by all commands
- Read references/workflows.md — multi-step patterns: author content, bulk ops, backup, CI
Known Limitations
- Status updates:
PATCH /artifacts/{id} silently ignores status when sent with other fields, and rejects it outright when sent alone. artifacts bulk-status and artifacts update --status will both fail. There is no known working API endpoint for changing artifact status — treat status as read-only for now.
- Artifact delete: The CLI has no
artifacts delete command. To delete, call DELETE $BASE_URL/artifacts/<id> directly with the Bearer token from ~/.config/artyfacts-pp-cli/config.toml.
Presenting results
- Lists: render as a table (id, title, type, status, updated_at).
- Single artifact: show metadata block then each section heading + body.
- Stats: prose summary ("23 artifacts: 8 specs, 6 docs, 5 reports…").
- Create/update: confirm what changed and show the artifact ID.
- Errors: show the message and suggest the fix (usually auth, sync, or a missing flag).
- After any create, offer the next logical step (add sections, mark active, sync).
1---2name: artyfacts3description: Manage your Artyfacts workspace — list, create, update, and search artifacts and sections via artyfacts-pp-cli. Invoke with /artyfacts <what you want to do>.4---56# /artyfacts78Work with your Artyfacts workspace using `artyfacts-pp-cli`.910```11/artyfacts # workspace overview12/artyfacts list my recent specs13/artyfacts create a feature spec for payments14/artyfacts search authentication15/artyfacts sync16/artyfacts show me stale artifacts17```1819## Step 1 — always check auth first2021```bash22artyfacts-pp-cli auth status23```2425If not authenticated:26```bash27artyfacts-pp-cli auth login28```2930## Step 2 — map intent to command3132| User says | Command group |33|-----------|---------------|34| list / browse / show / find | `artifacts list`, `artifacts tree` |35| search / look for | `search-local` (or `artifacts list --search`) |36| create / write / make | `workflow create-with-sections` or `artifacts create` + `sections create` |37| update / change / rename / move / archive | `artifacts update`, `sections update` |38| delete / remove a section | `sections delete` |39| delete an artifact | no CLI command — use `curl -X DELETE $BASE_URL/artifacts/<id>` with the Bearer token |40| bulk archive / promote / transition | `artifacts bulk-status` — **status-only PATCH is not supported by the API**; see Known Limitations |41| sync / refresh / pull | `sync` |42| stats / insights / who wrote what | `artifacts stats` |43| stale / out of date | `artifacts stale` |44| org settings / conventions | `org context` |45| export / backup | `export` |46| import / restore | `import` |47| log in / get key / check auth | `auth login`, `auth status` |4849**Valid artifact types:** `doc`, `spec`, `research`, `report`, `experiment`, `phase`, `runbook`, `folder`. Do not use `document` — it is rejected by the API.5051**Default output flag:** use `--json` whenever you need to parse or display structured data. Use `--agent` for non-interactive multi-step flows.5253**No arguments:** run `artifacts list --json`, `artifacts stats --json`, and `org context --json` to produce a workspace overview.5455## Reference files5657Load these when you need flag details, enumerations, or step-by-step examples:5859- Read [references/commands.md](references/commands.md) — full flag reference for every command60- Read [references/global-flags.md](references/global-flags.md) — output, behavior, and delivery flags shared by all commands61- Read [references/workflows.md](references/workflows.md) — multi-step patterns: author content, bulk ops, backup, CI6263## Known Limitations6465- **Status updates:** `PATCH /artifacts/{id}` silently ignores `status` when sent with other fields, and rejects it outright when sent alone. `artifacts bulk-status` and `artifacts update --status` will both fail. There is no known working API endpoint for changing artifact status — treat status as read-only for now.66- **Artifact delete:** The CLI has no `artifacts delete` command. To delete, call `DELETE $BASE_URL/artifacts/<id>` directly with the Bearer token from `~/.config/artyfacts-pp-cli/config.toml`.6768## Presenting results6970- **Lists:** render as a table (id, title, type, status, updated_at).71- **Single artifact:** show metadata block then each section heading + body.72- **Stats:** prose summary ("23 artifacts: 8 specs, 6 docs, 5 reports…").73- **Create/update:** confirm what changed and show the artifact ID.74- **Errors:** show the message and suggest the fix (usually auth, sync, or a missing flag).75- After any create, offer the next logical step (add sections, mark active, sync).
bmaltais