domains / families / software-engineering / writing-plans

writing-plans

combined

Use when you have a spec or requirements for a multi-step task, before touching code

When to use

• This skill is applicable to execute the workflow or actions described in the overview.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The obra/superpowers copy is the more complete and opinionated procedure: it adds a Scope Check, a File Structure section, Task Right-Sizing, a richer Plan Document Header (Spec path, Global Constraints, Review Focus), and an Interfaces block in each task. The other three copies (Vibe-Skills, agentic-awesome-skills, openclaw-master-skills) are near-identical to each other and share a simpler header, a 'questionable taste' framing, and an explicit Execution Handoff section that the obra copy does not include. Because the obra copy lacks the Execution Handoff and the other copies lack the Scope Check/File Structure/Interfaces/Review Focus material, crowning one would hide a real alternative.