Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

roadmap

Estrellas1

Forks0

Actualizado7 de julio de 2026 a las 12:54

Use when the user wants outcome-based delivery phases, exit criteria, or roadmap review at .agency/roadmap.md. Requires product.md for write. Do NOT use for epic breakdown or work paths (backlog), PRD (product), per-epic design (design), tasks (tasks), or architecture detail (solution).

Instalación

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.

Ejecutar en Manus

Fuente

carinyaparc

carinyaparc/digital-agency

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Especialistas en gestión de proyectosOperaciones empresariales y financieras·SOC 13-1082

Explorador de archivos

5 archivos

SKILL.md

readonly

name	roadmap
description	Use when the user wants outcome-based delivery phases, exit criteria, or roadmap review at .agency/roadmap.md. Requires product.md for write. Do NOT use for epic breakdown or work paths (backlog), PRD (product), per-epic design (design), tasks (tasks), or architecture detail (solution).
license	MIT
allowed-tools	["Read","Write","Glob","Grep"]
argument-hint	<mode: write\|review\|refine> [--context <notes>]

Roadmap

Artefact

Default path: .agency/roadmap.md — outcome-based phases with exit criteria.

Path resolution

If the user names a different file path in their request, read and write that path instead of the default.

Gotchas

Epic rows and work paths belong in backlog, not roadmap.
Story AC belongs in tasks.md, not phase exit criteria (keep exit criteria verifiable at phase level).

Supporting files

assets/roadmap.template.md

Related skills

product, backlog, solution

Router

Mode: write, review, or refine.
Resolve target path (default or user override).
One prompt under prompts/.

Más de este repositorio

mismo repositorio

setup

carinyaparc/digital-agency

Web development practice setup interview — detects or creates .agency/target.json binding, reads instance profile from `/agency-hub:setup`, interviews tech stack, deployment platform, connectors, and persona preference (six engineering personas vs merged), writes practice profile. Use on first install after `/agency-hub:setup`, when the user says "set up web development" or "bind target repo", or to redo engineering defaults only.

2026-07-071

ralph

carinyaparc/digital-agency

Use when the user wants to run a Ralph loop: an autonomous, self-referential delivery loop that drives a whole epic through implement, code review, fix, UX review, validate, commit, and merge request, one task per iteration, until a completion promise is emitted (ralph setup, ralph start), or to inspect or stop a running loop (ralph status, ralph cancel). Also supports simple ad-hoc loops that repeat a single prompt until done. Do NOT use to implement a single task once (implement), review a diff (code-review), or sign off an epic (validate) — the loop orchestrates those skills.

2026-07-071

ux-design-review

carinyaparc/digital-agency

Use when the user wants a UX/design review of implemented UI — frontend components, pages, or flows — against the design source of truth (Figma via MCP, mockups, tokens, or style guide, whatever the repo provides), covering design fidelity, accessibility (WCAG 2.2 AA), interaction states, responsiveness, and design-system conformity; or to address UX review findings (ux-design-review fix, optionally scoped to an action tier). Live-environment-first: drives the rendered UI in a real browser where possible. Works with any framework or design tooling. Do NOT use for code correctness/security review (code-review), to review a design.md document (design), or to implement features (implement).

2026-07-071

merge-request-review

carinyaparc/digital-agency

Use when the user is the reviewer of a merge request or pull request and wants it reviewed and the verdict published to the provider — inline comments on the right lines, threads resolved or replied to, and an approve / request-changes / comment decision. Handles first reviews and re-review rounds after the author pushes. Works with any codebase and any git provider — GitHub, GitLab, or Bitbucket — using MCP tools where available, provider CLIs otherwise. Do NOT use to review your own working diff before opening an MR (code-review), to open or babysit an MR (merge-request), or to implement changes (implement).

2026-07-071

merge-request

carinyaparc/digital-agency

Use when the user wants to open a merge request or pull request for the current branch (merge-request create — the default — with a generated title, description, labels, and reviewer suggestions), or to babysit an open MR/PR to a merge-ready state (merge-request babysit) by watching CI, review comments, and merge conflicts. Works with any codebase and any git provider — GitHub, GitLab, or Bitbucket — using MCP tools where available, provider CLIs otherwise, and plain git as a last resort. Do NOT use to review code or an MR as its reviewer (code-review, merge-request-review) or to implement changes (implement).

2026-07-071

code-review

carinyaparc/digital-agency

Use when the user wants a code review of a branch, PR, or diff against its acceptance criteria and declared scope (whatever form they take in this repo), or to address review feedback without changing behaviour (code-review fix, optionally scoped to a blocking or warning action tier). Works with any language, delivery process, or issue tracker. Do NOT use to implement code, sign off completion of a larger body of work, or review rendered UI/UX (design fidelity, accessibility — use ux-design-review).

2026-07-071

name	roadmap
description	Use when the user wants outcome-based delivery phases, exit criteria, or roadmap review at .agency/roadmap.md. Requires product.md for write. Do NOT use for epic breakdown or work paths (backlog), PRD (product), per-epic design (design), tasks (tasks), or architecture detail (solution).
license	MIT
allowed-tools	["Read","Write","Glob","Grep"]
argument-hint	<mode: write\|review\|refine> [--context <notes>]

Roadmap

Artefact

Default path: .agency/roadmap.md — outcome-based phases with exit criteria.

Path resolution

If the user names a different file path in their request, read and write that path instead of the default.

Gotchas

Epic rows and work paths belong in backlog, not roadmap.
Story AC belongs in tasks.md, not phase exit criteria (keep exit criteria verifiable at phase level).

Supporting files

assets/roadmap.template.md

Related skills

product, backlog, solution

Router

Mode: write, review, or refine.
Resolve target path (default or user override).
One prompt under prompts/.