| name | titan-capability-discovery |
| description | Inspect a project, plugin package, and Titan public docs to discover reusable workflow capabilities before creating new workflow code. Use when you need to know what workflows, steps, integrations, registration patterns, or ctx.textual capabilities already exist for a project or plugin. |
| disable-model-invocation | false |
| user-invocable | false |
Titan Capability Discovery
Inspect before inventing.
Goal
Identify what can be reused from:
- the current project's
.titan/
- a plugin package if the task targets a plugin
- Titan public docs
- existing workflow and step structure
Modes
Choose the right inspection mode first:
project
Inspect .titan/.
plugin
Inspect the plugin package and its registration flow.
public-plugin
Inspect the external or community plugin package layout and registration flow.
Inspection Order
Project mode
- Review
.titan/workflows/*.yaml.
- Review
.titan/steps/**/*.py.
- Review
.titan/operations/, .titan/clients/, and .titan/services/ if present.
Plugin mode
- Review the plugin package root.
- Review
plugin.py.
- Review workflow files under the plugin package.
- Review step registration modules if present.
- Review steps, operations, clients, services, and models.
Shared
- Review relevant public Titan docs when local package or project context is not enough.
Output
Return:
- Existing workflows worth extending or calling.
- Existing steps worth reusing.
- Existing project domains or integrations worth building on.
- Existing plugin registration patterns worth preserving.
- Missing pieces that actually need new code.
References
references/project-inspection-checklist.md
references/public-titan-capabilities.md
references/ctx-textual-capabilities.md