Menú
Use when invoking plannotator for approval review of generated .tff-cc milestone artifacts (plan, verification, spec).
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | plannotator-usage |
| description | Use when invoking plannotator for approval review of generated .tff-cc milestone artifacts (plan, verification, spec). |
∀ workflows that generate a load-bearing .md artifact under .tff-cc/milestones/ or .tff-cc/{quick,debug}/.
| Artifact | Workflow | Command | Notes |
|---|---|---|---|
| SPEC.md | /tff:discuss | invoke Skill plannotator-annotate with artifact path | Required |
| PLAN.md | /tff:plan, /tff:quick, /tff:debug | invoke Skill plannotator-annotate with artifact path | Required |
| VERIFICATION.md | /tff:verify | invoke Skill plannotator-annotate with artifact path | Required |
Excluded:
∀ points: opens interactive UI → user annotates → feedback returns to stdout → agent processes
allowed-tools: Skill(plannotator-annotate)
generate artifact → plannotator → user annotates → read feedback →
approved? → proceed
feedback? → revise → loop
claude /plugin install plannotator@plannotatorUse when making git commits. Conventional commit format and rules.
Use when running security review on a diff/PR/file. Research-vs-Reporting discipline, three-tier confidence gate, attacker-controllable taxonomy.
Use when starting design or discovery work. MUST use before any creative work.
Use when the user wants to report a bug, file an issue, or send feedback about tff-cc. Triggers on phrases like 'report issue', 'file a bug', 'tff-cc broke', 'something is wrong with tff-cc', 'open an issue', '/report-issue'.
Use when creating, refining, or composing skills. Evidence-driven pattern analysis.
Use when verifying acceptance criteria. Binary verdict per criterion. Evidence-based.