majiayu000 Writing Commands
Announce: "Using writing-commands skill for command creation, editing, or review."
Invariant Principles
- Commands are direct prompts: A command loads entirely into context. No phases dispatch to subagents. No orchestration layer. The agent reads it and does the work.
- Structure enables scanning: Agents under pressure skim. Sections, tables, and code blocks catch the eye. Prose paragraphs get skipped.
- FORBIDDEN closes loopholes: Every command needs explicit negative constraints. Agents rationalize under pressure. Each excuse needs a counter.
- Reasoning tags force deliberation:
<analysis>before action,<reflection>after. Without these, agents skip straight to output. - Paired commands share a contract: If command A creates artifacts, command B must know exactly how to find and remove them. The manifest/contract is the interface.
Inputs
| Input | Required | Description |
|---|---|---|
| Command purpose | Yes | What the command should accomplish when invoked |
| Trigger phrase | Yes | The /command-name that invokes it |
| Existing command | No | Path to command being reviewed or edited |
Outputs
| Output | Type | Description |
|---|---|---|
| Command file | commands/<name>.md |
Complete command following schema |
| Review report | Inline | Quality assessment against checklist (review mode) |
Phase Overview
| Phase | Name | Purpose | Command |
|---|---|---|---|
| 1 | Create | Schema, naming, required/optional sections, example, token efficiency | /writing-commands-create |
| 2 | Review | Quality checklist, anti-patterns, review protocol, testing protocol | /writing-commands-review |
| 3 | Paired | Paired command protocol, assessment framework integration | /writing-commands-paired |
Phase 1: Create Command
Define command structure using the schema: file naming, frontmatter, required sections, optional sections, and token efficiency targets.
Execute: /writing-commands-create
Outputs: Command file at commands/<name>.md
Self-Check: Frontmatter present, all required sections included, imperative language used, token targets met.
Phase 2: Review Command
Run the quality checklist against the command. Score structure, content quality, behavioral correctness, and anti-pattern avoidance. Follow the review and testing protocols.
Execute: /writing-commands-review
Outputs: Review report with score, passing/failing checks, critical issues.
Self-Check: All checklist items evaluated, score calculated, critical issues flagged.
Phase 3: Paired Commands
When a command creates artifacts, ensure a paired removal command exists with proper manifest, discovery, safety, and verification contracts.
Execute: /writing-commands-paired
Outputs: Paired command file, cross-references in both commands.
Self-Check: Manifest format defined, both commands cross-reference each other, removal is safe.
Self-Check
Before completing command creation or review:
- Frontmatter has
descriptionfield with triggers, not workflow - MISSION section is one clear paragraph
- ROLE tag has domain expert + stakes
- 3-5 Invariant Principles, each testable
- Execution steps are numbered and imperative
- Every step that can fail has a failure path
- Output section has concrete format
- FORBIDDEN section has 5+ specific prohibitions
- Analysis tag prompts pre-action reasoning
- Reflection tag asks specific verification questions
- If paired: partner command referenced, manifest format defined
If ANY unchecked: STOP and fix before declaring complete.