Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

roadmap

Estrelas2

Forks0

Atualizado19 de julho de 2026 às 12:05

Use when the user wants outcome-based delivery phases, exit criteria, or roadmap review at docs/product/roadmap.md. Two modes: write (draft or re-sequence) and review (judge credibility, record delivery evidence, amend in place). Triggers on "build the roadmap", "what are our delivery phases", "phase exit criteria", "is this roadmap credible", "did we hit the phase gate". Requires product.md for write. Do NOT use for epic breakdown or work paths (tasks), PRD (product), per-epic design (design), tasks (tasks), or architecture detail (solution).

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

carinyaparc

carinyaparc/skills

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Especialistas em gestão de projetosNegócios e Operações Financeiras·SOC 13-1082

Explorador de arquivos

4 arquivos

SKILL.md

readonly

name	roadmap
description	Use when the user wants outcome-based delivery phases, exit criteria, or roadmap review at docs/product/roadmap.md. Two modes: write (draft or re-sequence) and review (judge credibility, record delivery evidence, amend in place). Triggers on "build the roadmap", "what are our delivery phases", "phase exit criteria", "is this roadmap credible", "did we hit the phase gate". Requires product.md for write. Do NOT use for epic breakdown or work paths (tasks), 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> [--context <notes>]
metadata	{"author":"Carinya Parc","version":"1.0","owner":"product","work_shape":"planning","output_class":"delivery-artefact"}

Roadmap

Artefact

Default path: docs/product/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, tasks, solution

Router

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

Mais deste repositório

mesmo repositório

skill-review

carinyaparc/skills

Use when the user wants to research, review, or enhance an agent skill on a regular cadence — weekly skill uplift, audit a SKILL.md against best practice, compare with popular external skills, fix working issues, or align with agentskills.io. Triggers on "review this skill", "enhance the X skill", "weekly skills review", "uplift this skill", "align with agentskills.io". Works on one skill or a batch. Do NOT use to create a skill from scratch (create-skill / author a new skill), route which skill to use (skills-index), or review product documentation (docs-review).

2026-07-192

adr

carinyaparc/skills

Use when the user wants ADR register planning, writing ADR-NNNN files, or ADR review under docs/architecture/decisions/. Triggers on "do we need an ADR", "write ADR-0007", "record this decision", "what decisions need making", "harvest ADRs from this epic". Do NOT use for full architecture narrative (solution), epic design (design), or product strategy (product). Proposals stay in register.md only until accepted.

2026-07-192

backlog-refine

carinyaparc/skills

Use to groom an existing backlog or judge whether a breakdown is ready to commit to — reprioritise, split oversized epics or stories, re-estimate, defer misaligned items, and check sprint readiness of docs/product/backlog.md or docs/work/{epic}/tasks.md. Triggers on "groom the backlog", "refine the backlog", "is this sprint-ready", "are these stories ready", "reprioritise", "this epic is too big", "clean up the backlog". Amends in place and reports a verdict. Do NOT use to create a backlog or write new stories and tasks (tasks), plan a sprint (sprint-planning), review a finished sprint (sprint-retro), or verify an epic against its acceptance criteria (validate).

2026-07-192

code-review-fix

carinyaparc/skills

Use when the user wants to address, action, or fix findings from a code review — their own working diff reviewed by code-review, a reviewer's comments on a PR or MR, or a pasted list of issues. Triggers on "fix the review findings", "address the review feedback", "action the blocking issues", "apply the review comments". Optionally scoped to an action tier (blocking, warning, all). Makes targeted, behaviour-preserving changes, runs the project's validation suite, and commits in logical units. Do NOT use to perform a review (code-review), to implement new work or features (implement), to address UX or design-fidelity findings (ux-design-review), or to open a PR/MR (merge-request).

2026-07-192

code-review

carinyaparc/skills

Use when the user wants a code review of a branch, PR, MR, or working diff against its acceptance criteria and declared scope, in whatever form they take in this repo. Triggers on "review my branch", "review this PR", "check this diff before I raise it", "is this ready to merge". Works with any language, delivery process, or issue tracker. Produces a structured verdict with blocking, warning, and suggestion findings; writes no source changes. Do NOT use to address or fix review findings (code-review-fix), to implement work (implement), to publish a review to a provider as its reviewer (merge-request-review), to sign off completion of a larger body of work (validate), or to review rendered UI (ux-design-review).

2026-07-192

design

carinyaparc/skills

Use when the user wants epic-level technical design at docs/work/{epic}/design.md, walking-skeleton or TDD design, or design review before tasks. Pass epic slug or ID (CHK01). Cite solution.md — do not re-narrate architecture. Triggers on "design CHK01", "write the epic design", "how should we build this epic", "review the design before tasks". Do NOT use for epics or stories (tasks), task Gherkin (tasks), system-wide architecture (solution), ADR write (adr), code implementation (implement), or reviewing a set of documents for quality and consistency (docs-review).

2026-07-192

name	roadmap
description	Use when the user wants outcome-based delivery phases, exit criteria, or roadmap review at docs/product/roadmap.md. Two modes: write (draft or re-sequence) and review (judge credibility, record delivery evidence, amend in place). Triggers on "build the roadmap", "what are our delivery phases", "phase exit criteria", "is this roadmap credible", "did we hit the phase gate". Requires product.md for write. Do NOT use for epic breakdown or work paths (tasks), 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> [--context <notes>]
metadata	{"author":"Carinya Parc","version":"1.0","owner":"product","work_shape":"planning","output_class":"delivery-artefact"}

Roadmap

Artefact

Default path: docs/product/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, tasks, solution

Router

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