Skills

Install and use Cocurdex product skills (cocurdex-*) for notes, issues, slide decks, teams, settings, and shipping work.

Product skills teach agents how to work with Cocurdex notes, issues, slide decks, and the product knowledge flow. Skill names are namespaced with the cocurdex- prefix so they do not clash with other global skills.

Skills are not auto-installed. Install from Settings → Skills in the desktop app, or from the CLI.

Install

cocurdex skills list
cocurdex skills status --scope project
cocurdex skills install --scope project
# or for your user-wide skills directory
cocurdex skills install --scope global

Scope	Meaning
`project`	Install under the project root (`--root` defaults to `cwd`)
`global`	Install into the user global skills location

Managed installs write a marker file so Cocurdex can update or remove its own pack. Updating a managed install also deletes skills that were retired from the pack, so old names do not linger. If skills already exist without that marker, install reports a conflict — rename or remove the conflicting folders and retry.

cocurdex skills remove --scope project

Skill catalog

Skill	Purpose
`cocurdex-note`	Create, update, and link notes — including PRDs and technical specs — through the CLI
`cocurdex-issue`	Create, list, move, and refine issues; also answers to “todo”, “ticket”, and “backlog”
`cocurdex-deck`	Create and revise slide decks, check them, and export PPTX or PDF. Invoke it as `/cocurdex-deck`
`cocurdex-ship`	Implement an issue or spec note, run the project's checks, and move the issue through its columns. You invoke it explicitly; agents do not start it on their own
`cocurdex-team`	Lead an agent team: decide when a team helps, brief teammates, merge their reports
`cocurdex-settings`	Inspect and change app and project settings through the `settings_*` agent tools

Todo, ticket, and backlog item all mean issue — one pool, not separate trackers.

Retired skills

Earlier packs also shipped cocurdex-ask, cocurdex-grill, cocurdex-prd, cocurdex-spec, cocurdex-todo, cocurdex-ticket, cocurdex-link, and cocurdex-layout. Their useful parts were folded into cocurdex-note and cocurdex-issue; reinstalling or updating the pack removes the old folders.

Recommended product flow

/cocurdex-note   (PRD or spec as a note)
  → /cocurdex-issue  (slice into issues)
  → /cocurdex-ship   (implement one issue)

Step	Skill	Writes
Requirements and design	`/cocurdex-note`	Private notes (PRDs, specs, free-form)
Board work	`/cocurdex-issue`	Issues via `cocurdex issue …`
Implement	`/cocurdex-ship`	Code + issue status updates

Slide decks sit beside that loop. /cocurdex-deck writes them with cocurdex deck.

Privacy default

PRDs, specs, notes, issues, and slide decks are private app-owned data. Opening a project folder is not permission to dump product docs into .cocurdex/ or Markdown trees; publishing a note into a repository needs an explicit export.

Issue structure (list / create / move / validate) always goes through:

cocurdex issue …

Skills must not invent issue ids or rewrite status by hand-editing files.

Using skills in a session

Install the skill pack (project or global).
Start an agent session that can load skills from that location.
Invoke with the slash form your agent supports (for example /cocurdex-issue), type / in the composer, or pick one from the composer's + → Skill menu.
Attach an issue or note from + → Issue / + → Note: the agent receives its full content in the prompt, so the skill does not need to fetch it again.

Other non-product skills (tdd, code review, etc.) may still exist in your environment; product knowledge work should stay on the cocurdex-* set so data boundaries stay correct.