titan-project-workflow-builder

Generates project-specific Titan workflow scaffolds from user requirements.

7|3|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/masorange/titan-cli --skill titan-project-workflow-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: titan-project-workflow-builder
Source: https://github.com/masorange/titan-cli/tree/main/.claude/skills/titan-project-workflow-builder
Command: npx skills add https://github.com/masorange/titan-cli --skill titan-project-workflow-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Designing and scaffolding project-specific Titan workflows under the .titan directory, translating user requirements into concrete workflow artifacts.

Core Features & Use Cases

  • Project-scoped workflow design: converts user goals into .titan/workflows, .titan/steps, and project-domain code under .titan/operations, .titan/clients, and .titan/services.
  • Architecture-first generation: prioritizes minimal, correct architecture while reusing existing Titan capabilities.
  • Template-driven implementation: provides starter templates and decision guidance for workflow files and references.

Quick Start

Describe your project goal and I will generate a starter .titan workflow scaffold.

Frequently Asked Questions about titan-project-workflow-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate YAML workflows for a project?

You can scaffold project workflows by describing your project goal, which generates .titan/workflows YAML files. The system automatically maps requirements into steps, operations, clients, and services under a project namespace.

What is the best way to structure reusable domains in a workflow orchestration project?

Organize reusable domains under a project namespace within .titan/operations, .titan/clients, and .titan/services. This architecture-first approach ensures minimal, correct structuring while reusing existing capabilities.

How do I add hooks and parameters to an existing YAML workflow?

Extend existing YAML workflows by following provided decision guidance for project steps. The system enforces Titan semantics for hooks, params, result types, and cleanup to ensure your workflow extensions remain valid.

Does the workflow scaffolding process require manual setup for cleanup and result types?

No, manual setup is not required. The scaffolding process automatically enforces Titan semantics for hooks, params, result types, and cleanup during the workflow generation to ensure correct implementation.

Can I use this workflow builder for project-local domain code generation?

Yes, this builder is designed for project-local work. It generates YAML workflows, creates steps, and organizes reusable domain code under your project's local .titan directory structure.