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.
Design and create workflows for official Titan plugins inside the titan-cli repository. Use when adding or changing workflows in plugins/titan-plugin-*, registering plugin steps, or extending official plugin capabilities that stay inside this repository.
Design and create Titan workflows for a specific project under .titan/. Use when the user wants a workflow in .titan/workflows, project steps under .titan/steps, or project-scoped operations, clients, and services.
Design and create workflows for public or community Titan plugins intended for external users. Use when adding workflows to a plugin package that will be distributed outside its current repository.
Choose the correct Titan architecture for new workflow code. Use when deciding between command steps, project steps, operations, clients, services, plugin registration, or project versus plugin layout, or when the user asks how much architecture is justified.
Guide for creating new Claude skills following Anthropic's best practices. Use when user says "create a skill", "new skill", "build a skill", "skill for X", or asks about "how to create skills", "skill structure", "skill best practices", "skill guidelines".
Write comprehensive tests for Titan CLI plugins - unit tests, fixtures, mocks, and coverage strategies. Use when user says "write tests", "test this", "add unit tests", "create fixtures", "test coverage", or asks about "how to test", "pytest", "mocking", "test strategy".