fx-workflow-authoring

Codify CC-native doctrine for authoring and refactoring tk-* workflow skills.

Updated May 19, 2026
One-click install
npx skills add https://github.com/TimeKast/AgendaInteligente --skill fx-workflow-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fx-workflow-authoring
Source: https://github.com/TimeKast/AgendaInteligente/tree/main/.claude/skills/fx-workflow-authoring
Command: npx skills add https://github.com/TimeKast/AgendaInteligente --skill fx-workflow-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It standardizes how to write and refactor CC-native pipeline workflows so each new tk-* skill follows the same contracts, checkpoints, artifacts, and subprocess delegation rules—without silent behavioral drift.

Core Features & Use Cases

  • Workflow authoring doctrine for creating tk-* orchestration skills and thin slash commands in .claude/skills/tk-* and .claude/commands/.
  • Checkpoint design discipline (CP1 inline STOP and CP2 Plan Mode) including numbered options and explicit invalidation handling.
  • Artifact + templates enforcement using a hard “no template, no artifact” rule to keep output shapes stable across versions.
  • Subprocess delegation policy defining when to isolate work into subprocess agents, including scoped naming and tool allowlists.

Quick Start

Invoke fx-workflow-authoring to design or refactor a new tk-* workflow’s phases, checkpoints, templates, and wrapper so it passes the heavy checklist.

Frequently Asked Questions about fx-workflow-authoring

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

FAQPage Schema
How do I standardize workflow authoring to prevent behavioral drift across orchestration skills?

Workflow authoring doctrine standardizes how orchestration skills are written by enforcing mandatory SKILL.md frontmatter contracts, canonical section ordering, and subprocess delegation rules to prevent silent behavioral drift across versions.

What is checkpoint design and how do I implement gating with numbered options?

Checkpoint design implements discipline through CP1 inline STOP and CP2 Plan Mode gating with numbered options and explicit invalidation handling, ensuring controlled phase transitions and preventing undesired workflow progression.

How do I enforce artifact templates when authoring pipeline workflows?

Artifact templates are enforced using a hard "no template, no artifact" rule during workflow creation and validation, keeping output shapes stable and predictable across all versions of the pipeline workflow.

When should I isolate work into subprocess delegation for agents?

Subprocess delegation should isolate work into agents when you need scoped naming and tool allowlists, defining explicit boundaries for subprocess skill grounding using repo-relative paths to maintain execution isolation.

Does workflow authoring support refactoring existing orchestrator skills and slash commands?

Workflow authoring supports refactoring existing orchestrator skills and thin slash commands by applying codified doctrine during phase refactoring, checkpoint design, and template validation within the command directory structure.