CC roadmap-producto-f100k
Construye el ROADMAP de un programa, curso, comunidad, servicio o producto físico con Backward Design (ingeniería inversa desde la promesa final). Diseña el viaje del cliente — punto A a punto B — en fases con objetivos y entregables medibles. Soporta 4 tipos: digital (curso), comunidad (Skool), servicio (consultoría/coaching 1:1) y producto físico. Activar SIEMPRE que se pida 'hazme un roadmap', 'arma el roadmap de mi curso', 'diseña el paso a paso de mi programa', 'metodología de mi formación', 'cómo estructuro mi curso', 'fases de mi comunidad', 'arquitectura de mi programa', 'ingeniería inversa de mi promesa', 'backward design', 'estructura mi mentoría/consultoría', 'onboarding de mi producto físico', o cualquier variación de estructurar el VIAJE/CONTENIDO del producto. NO usar para la OFERTA de venta (constructor-ofertas-f100k), copy de venta (vsl-expert-f100k) ni calendarios de contenido (calendarizador-contenido-formula100k). Es el paso PREVIO a constructor-ofertas-f100k.
Construye el ROADMAP de un programa, curso, comunidad, servicio o producto físico con Backward Design (ingeniería inversa desde la promesa final).
As a process C 58/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 58/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 4638 tokens
- 85Steps. 108 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- low 12 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 993: 120–800 characters recommended
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +4Structure: 39 headings
- +3Step-by-step instructions: 108 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.