What is quinotospec-create-user-stories?

A workflow that turns an existing technical proposal into user stories: short descriptions of what different people or systems need to do.

Use it to create or update user stories from a proposal, identify the roles involved, and order stories according to the proposal’s implementation plan.

It removes the manual step of translating a proposal into organized requirements. It also preserves existing stories by merging only new or changed ones.

quinotospec-create-user-stories — Skill for Cursor by Quinoto-Tech

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

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

agentmods

npx agentmods add skills/quinoto-tech/quinotospec/quinotospec-create-user-stories

Made for: Cursor.

Or install quinotospec, the plugin that ships this one along with the rest of its 90 skills, 9 agents, 1 hook.

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-user-stories/github.svg)](https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-create-user-stories)

Your own site

<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-create-user-stories"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-create-user-stories/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-user-stories"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-create-user-stories.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 897 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00018	$0.00897
Opus 5.5	$0.00007	$0.00359
Sonnet 5.5	$0.00004	$0.00179
Haiku 4.5	$0.00002	$0.00090

Measured 1mo ago against content hash c16eaa26b6f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

quinotospec-create-user-stories 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 1mo 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-user-stories/SKILL.md · 50 lines

What it actually says

Workflow: Create User Stories

Este workflow genera user stories derivadas de una propuesta técnica existente. Requiere que la propuesta (proposal.md) ya haya sido creada.

Parámetro Requerido:

PROPOSAL_SLUG: El nombre de la carpeta de la propuesta (ej. refactor-proposal-workflows).

Instrucciones:

Lee el archivo .quinoto-spec/proposals/{{PROPOSAL_SLUG}}/proposal.md.
Validación previa: Verifica que el **Estado:** de la propuesta NO sea Archivada. Si lo es, notifica al usuario y detén el proceso.
Inferencia de roles: Identifica los roles involucrados a partir del contenido de la propuesta y de 01-stack-profile.md en el discovery (ej. usuario, admin, sistema, operador). Úsalos en las stories en lugar de [rol] genérico.
Cantidad de stories: Genera una story por cada funcionalidad o cambio sustancial de la propuesta. Ordénalas según las fases del Plan de Implementación definido en la propuesta.
Merge inteligente: Si .quinoto-spec/proposals/{{PROPOSAL_SLUG}}/user-stories.md ya existe, no sobreescribas. Revisa las stories existentes y realiza un merge: agrega solo las stories nuevas y actualiza las que hayan cambiado.
Antes de escribir, valida el contrato de la propuesta:
```
python3 agent-dist/skills/quinotospec-contract/contract.py validate --root . --strict
```
Si el prefijo, la fecha o el estado no son recuperables, detén el workflow.
Genera el archivo en .quinoto-spec/proposals/{{PROPOSAL_SLUG}}/user-stories.md usando agent-dist/templates/user-stories-template.md:
- Título: User Stories ({{PROPOSAL_NAME}}).
- Tabla con columnas: ID, User Story, Criterios de Aceptación, Prioridad, Estimación, Servicio.
- IDs: Usa IDs canónicos US-{{PREFIX}}-001; {{PREFIX}} conserva el mnemónico y el sufijo completo.
- Estado: No agregues una columna de estado; se deriva de las tareas asociadas.
- Prioridad: P1 (alta) / P2 (media) / P3 (baja), según la fase y relevancia en la propuesta.
- Estimación: Talla de camiseta (XS / S / M / L / XL) según la complejidad estimada de la historia.
- Servicio: El sub-proyecto o servicio donde se implementa esta historia, inferido de **Servicios Afectados:** en proposal.md. Si la historia aplica a todos los servicios, usar todos.
- Template canónico:
```
# User Stories ({{PROPOSAL_NAME}})

**Proposal ID:** {{PROPOSAL_ID}}
**Prefijo:** {{PREFIX}}
**Estado:** proposed

| ID | User Story | Criterios de Aceptación | Prioridad | Estimación | Servicio |
|---|---|---|---|---|---|
| US-{{PREFIX}}-001 | Como **[rol]**, quiero **[acción]**, para **[beneficio]**. | - [ ] Criterio verificable 1<br>- [ ] Criterio verificable 2 | P1 | M | auth-service |
```

Instrucción Final OBLIGATORIA (Changelog): Una vez completada, DEBES ejecutar la skill quinotospec-update-changelog.

Título de la Acción: User Stories Generated: {{PROPOSAL_NAME}}
Resumen: Se generaron user stories para la propuesta '{{PROPOSAL_NAME}}' en .quinoto-spec/proposals/{{PROPOSAL_SLUG}}/

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.

1mo ago Changed · +9 lines c16eaa26b6f8
2mo ago First seen · 41 lines · 18 tokens per session scan A 6344ab6d0cab

Subscribe to this mod's changes

quinotospec-create-user-stories is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (21 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 897 once invoked, about $0.0001 per session on Opus 5.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.

Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens