The /para-workflow command is a specialized management tool for the Workflow Library. Unlike daily execution commands, this workflow is used to maintain, install, and design the “blueprints” that guide AI behavior.
Command List
/para-workflow [action] [name]| Action | Description |
|---|---|
list | Compare Local workflows against the Governed Catalog. |
add | Initialize a new PARA-compliant workflow draft. |
standardize | Upgrade workflows to meet the latest architecture. |
install | Fetch official workflows from the Catalog. |
validate | Check for syntax errors and compliance issues. |
Workflow Standardization (8-Point Checklist)
To ensure a workflow is both efficient and safe, it must pass an 8-point quality check:
- YAML Frontmatter: Must include a mandatory
descriptionfield. - Version Label: Must accurately display the current version.
- Language: Core instructions should prioritize English for optimal Agent reasoning.
- Relative Paths: Strictly no absolute paths allowed.
- Project Placeholders: Use
[project-name]variables instead of hardcoded strings. - Catalog Paths: Must point to the correct administrative Catalog source.
- Turbo Annotations: Use
// turbofor safe steps the Agent can auto-execute. - No Duplicate Scope: Ensure logic doesn’t overlap with existing system commands.
Critical Notes
- Source of Truth: The
catalog.ymlfile defines the only officially supported workflows. - Untracked Workflows: You can create custom workflows; they remain functional but are labeled “untracked” and won’t receive automatic system updates.
- Maintenance: Run
validateregularly to identify legacy paths or deprecated instructions.
Relationships
/para— Overall Workspace Master Controller./para-rule— Management of behavioral rules./merge— Merging custom logic when a new Catalog version is available.