What is quinotospec-create-tasks?

A workflow that turns user stories into a technical task plan. User stories describe needs from a person’s or system’s point of view; tasks describe the implementation work.

Use it to generate tasks for all stories or one selected story, optionally reading the stories from an RFC instead of a proposal.

It connects product requirements to concrete engineering work and supports either proposal-based or RFC-based planning.

quinotospec-create-tasks — Skill for Claude Code and Codex by Quinoto-

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add Quinoto-Tech/QuinotoSpec --skill quinotospec-create-tasks

Clone the repo

git clone --depth 1 https://github.com/Quinoto-Tech/QuinotoSpec

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-create-tasks/github.svg)](https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-create-tasks)

Your own site

<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-create-tasks"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-create-tasks/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-create-tasks"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-create-tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,423 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00024	$0.02423
Opus 5	$0.00012	$0.01211
Sonnet 5	$0.00005	$0.00485
Haiku 4.5	$0.00002	$0.00242

Measured 12d ago against content hash ecdbc12ab7db, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

quinotospec-create-tasks scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

agent-dist/skills/quinotospec-create-tasks/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Workflow: Create Tasks

Este workflow genera un plan de tareas técnicas derivado de user stories.

Dos orígenes de contexto (usa uno u otro, no ambos):

Origen	Requisito	Carpeta de trabajo
Propuesta (modo clásico)	`user-stories.md` bajo la propuesta	`.quinoto-spec/proposals/{{PROPOSAL_SLUG}}/`
RFC (`--from-rfc`)	RFC generado por `quinotospec.create-rfc` con la seccion `## User Stories (entrada para create-tasks)`	`.quinoto-spec/rfc/{{RFC_STEM}}/`

Parámetros Requeridos:

Modo propuesta (por defecto): PROPOSAL_SLUG — nombre de la carpeta de la propuesta (ej. refactor-proposal-workflows).
Modo RFC: --from-rfc + RFC_PATH — ruta al archivo Markdown del RFC (ej. .quinoto-spec/rfc/RFC-20260427-mi-slug-mi-feature.md). En este modo no uses PROPOSAL_SLUG.
USER_STORY_ID: (Requerido si se usa --single) El ID de la user story objetivo (ej. US-AUTH-a1b2-001).

Flags:

--from-rfc <RFC_PATH>: Lee el RFC y la tabla de historias incrustada; escribe tareas bajo .quinoto-spec/rfc/{{RFC_STEM}}/. RFC_STEM = nombre del archivo del RFC sin extension .md.
--single -s: Genera tareas solo para una user story específica (contrario al comportamiento por defecto).
Si no se especifica --single, se genera tareas para TODAS las user stories pendientes del origen activo (propuesta o RFC).

Instrucciones:

Modo RFC (`--from-rfc`) — Tareas desde un RFC

Usar cuando el plan de valor ya esta descrito en el RFC (flujo quinotospec.create-rfc) y no hace falta una carpeta de propuesta todavia.

Resolver y leer RFC_PATH (ruta absoluta o relativa a la raiz del repo).
Calcular RFC_STEM: nombre del archivo sin .md (ej. RFC-20260427-mi-slug → stem igual al basename completo).
Definir RFC_BUNDLE_DIR = .quinoto-spec/rfc/{{RFC_STEM}}/. Si no existe, crearlo.
Localizar en el RFC el heading exacto ## User Stories (entrada para create-tasks).
- Si no existe: detener con mensaje claro: completar esa seccion segun quinotospec.create-rfc o copiar el formato de quinotospec.create-user-stories.
Debajo del heading, parsear:
- La linea **Prefijo (QuinotoSpec):** (aceptar tambien **Prefijo:** si el contenido es el mismo formato MNEM-xxxx).
- La tabla markdown (columnas: ID, User Story, Criterios de Aceptacion, Prioridad, Estimacion, Servicio).
Materializar user stories en el bundle (merge inteligente):
- Archivo objetivo: {{RFC_BUNDLE_DIR}}/user-stories.md.
- Si no existe: crearlo con titulo User Stories (RFC: {{RFC_STEM}}) y el cuerpo de tabla parseada (mismo formato que en modo propuesta).
- Si ya existe: no sobreescribas; haz merge como en modo propuesta (agregar/actualizar filas segun la tabla del RFC).
Contexto tecnico sustituto de proposal.md: usar el texto completo del RFC como fuente principal, priorizando secciones de propuesta tecnica, impacto, plan de implementacion, riesgos, pruebas y "Proposal Seed" si estan presentes.
A partir de aqui, aplica la misma logica que en Modo Individual o Modo Bulk, pero sustituyendo siempre:
- .quinoto-spec/proposals/{{PROPOSAL_SLUG}}/ → {{RFC_BUNDLE_DIR}}/
- PROPOSAL_NAME → titulo del RFC (primer # del documento, o TITLE del template, o RFC_STEM si no hay titulo claro).
Archivo consolidado opcional: {{RFC_BUNDLE_DIR}}/all_tasks.md con la misma regla que en modo bulk (solo si no existe o si el usuario lo pide).

Read the full file on GitHub · 108 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

12d ago First seen · 108 lines · 24 tokens per session scan A ecdbc12ab7db

Subscribe to this mod's changes

quinotospec-create-tasks is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (20 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 2,423 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens