cft-workspace

Summarise one HMCTS service's OpenAPI spec from cnp-api-docs. Reports title, version, auth, endpoint count by tag, owning product, hosted Swagger UI link, and local file path. Use when the user asks "what does pcs-api expose", "summarise ccd-data-store-api", "what auth does X use", "show me the endpoints of Y".

Find every product that uses a given CCD feature token (e.g. notice_of_change, case_flags). Use when the user asks "which services use X", "who has NoC enabled", "what products configure case flags".

Trace a CCD callback for a given event-id and service from definition through to controller. Returns the chain of file:line locations. Use when the user wants to know what runs when an event is submitted in a specific service.

Search across all cloned HMCTS repos using the workspace's pre-tuned ripgrep wrapper. Use when the user asks about code or text patterns spanning multiple service teams or platform components.

Answer a "what is X" / "how does Y work" / "explain Z" question about any CFT topic — workspace, CCD, XUI, WA, AM, bulk-scan, platform/CNP. Routes via DOCS.md to the right page in either the root docs/ tree or a product-level apps/<product>/docs/ tree.

Find which HMCTS API service exposes a given HTTP path. Searches cnp-api-docs for matching OpenAPI paths and reports the owning service, methods, the local spec file, the hosted Swagger UI link and the workspace product that publishes it. Use when the user asks "which service has POST /cases/{id}/...", "what exposes /hearings", "where is /case-types defined", etc.

Find real, in-repo examples of how a feature is implemented in any HMCTS CFT product (CCD, XUI, WA, AM, bulk-scan, service teams). Use when the user wants concrete code references — "show me a real Notice of Change implementation", "where do they use case_flags", "give me an example of a mid-event callback".

Find a Diátaxis how-to recipe for an action-shaped task across the workspace docs. Use when the user asks "how do I add an event in CCD", "where do I configure work allocation tasks", "how do I add a repo", "how do I publish a definition to AAT".

List every workspace product that integrates with a given platform — work_allocation, bulk_scan, bulk_print, payment, send_letter etc. Use when the user asks "who integrates with X", "which services use payment", "what consumes work allocation".

Give a guided tour of a workspace product — purpose, constituent repos, cross-repo wiring, and the first files a new contributor should read. Use when the user asks "tour me through nfdiv", "introduce me to ccd", "what is wa", "give me a walkthrough of pcs".

Detect documentation drift across the workspace. Three modes — source-citation (sources: frontmatter vs cited file SHAs), port-manifest (docs/ vs upstream platops/hmcts.github.io), Confluence-revision (cached Confluence pages vs current revisions). Use when the user asks "what docs need updating?", periodically as a maintenance check, or after pulling new commits into a source repo.

Regenerate product-level CLAUDE.md files and refresh INDEX.md. Fans out the product-analyser subagent across every product directory in the workspace, then runs ./scripts/index. Use when the user asks to populate, refresh, or re-run the workspace taxonomy, asks "what's in the workspace?", or when INDEX.md looks stale — and as the first step to make /cft-ccd-find-feature, /cft-list-integrations, and /cft-tour useful.

Generate (or refresh) comprehensive documentation under apps/<product>/docs/ for any workspace product (ccd, am, xui, wa, bulk-scan, send-letter, em, payment, rd, …). Use when the user asks to populate, refresh, or extend a product's docs, or when a source repo has changed and pages need re-verifying.