output-conventions

What problem does it solve?

Inconsistent file outputs, scattered artifacts, and the creation of unnecessary temporary files can clutter projects and hinder collaboration. This skill defines strict output conventions to maintain project hygiene and clarity.

Core Features & Use Cases

• Structured Output: Mandates specific file structures for project (.plan/), memory (.claude/), and plugins (.claude-plugin/) artifacts.
• File Creation Rules: Specifies which files must always be created (e.g., state.json, tasks.md) and which must never be created (e.g., README.md, .backup).
• Output Validation: Guides on validating outputs before finalization, including checking for duplicates and parasite files.
• Use Case: After an agent completes a phase (e.g., Architecture), use this skill to ensure all generated artifacts are correctly placed in .plan/architecture.md and state.json, and that no unauthorized files are created, maintaining project hygiene and consistency.

Quick Start

Use the output-conventions skill to verify the correct structure for project output files in the '.plan/' directory.