cursor-workflow

Consolidating Cursor IDE workflow helpers requires creating a non-stub SKILL.md with YAML frontmatter, trigger mappings, documented dependencies, and a complete operational body before promotion. This unifies developer tooling scenarios and improves discoverability of IDE automation capabilities.

A stub skill in IDE automation is a registered placeholder that explicitly marks itself as unimplemented to ensure safety-by-design. It prevents accidental invocation as a real operational skill while documenting future build promotion requirements like triggers and end-to-end validation.

Setting up trigger phrases for a Cursor developer tooling skill involves documenting them within a non-stub SKILL.md file. This file must include YAML name and description frontmatter, explicit trigger mappings, and documented dependencies to ensure proper IDE automation activation.

No, the cursor-workflow skill does not currently solve actionable developer tasks. It serves as a placeholder for consolidating Cursor IDE-side helper skills and provides a build promotion checklist for future implementation including triggers and end-to-end validation.

You should defer invoking a Cursor IDE workflow helper when the skill remains in the _deferred folder as a stub. Invocation should wait until the build checklist is completed and the folder is promoted out of _deferred with full operational capabilities.

Before promoting a developer tooling skill, you need to validate triggers, dependencies, and end-to-end functionality. The skill must transition from a stub to a complete operational body with documented inputs and outputs in its SKILL.md file.