Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

solution

Étoiles1

Forks0

Mis à jour6 juillet 2026 à 12:53

Use when the user wants to write, review, or refine system architecture at .agency/architecture/solution.md (stub or full arc42-lite). Do NOT use for business strategy (product), delivery phases (roadmap), epic list (backlog), per-epic design.md (design), task Gherkin (tasks), or ADR files (adr write). Story AC belongs in .agency/work/{epic}/tasks.md.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

carinyaparc

carinyaparc/digital-agency

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

5 fichiers

SKILL.md

readonly

name	solution
description	Use when the user wants to write, review, or refine system architecture at .agency/architecture/solution.md (stub or full arc42-lite). Do NOT use for business strategy (product), delivery phases (roadmap), epic list (backlog), per-epic design.md (design), task Gherkin (tasks), or ADR files (adr write). Story AC belongs in .agency/work/{epic}/tasks.md.
license	MIT
allowed-tools	["Read","Write","Glob","Grep"]
argument-hint	<mode: write\|review\|refine> [--stage stub\|full] [--context <notes>]

Solution

Conventions

Read ../../references/web-development-conventions.md for artefact boundaries.

Artefact

Default path: .agency/architecture/solution.md — arc42-lite architecture (stub or full).

Path resolution

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

Stage (write mode)

Stage	When	Sections
`stub`	Phase 0	§1–§2 only; §3–11 scaffolded
`full`	Phase 2+	All eleven sections

Gotchas

Per-epic files/APIs → cite from .agency/work/{epic}/design.md, don't duplicate full specs.
Story-level Gherkin → tasks.md, not solution.
Closed ADRs → ADR-NNNN-*.md; proposals stay in register only.

Supporting files

assets/solution.template.md

Related skills

product, backlog, tasks, design, adr

Router

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

write — --stage stub|full.

Plus depuis ce dépôt

même dépôt

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	solution
description	Use when the user wants to write, review, or refine system architecture at .agency/architecture/solution.md (stub or full arc42-lite). Do NOT use for business strategy (product), delivery phases (roadmap), epic list (backlog), per-epic design.md (design), task Gherkin (tasks), or ADR files (adr write). Story AC belongs in .agency/work/{epic}/tasks.md.
license	MIT
allowed-tools	["Read","Write","Glob","Grep"]
argument-hint	<mode: write\|review\|refine> [--stage stub\|full] [--context <notes>]

Solution

Conventions

Read ../../references/web-development-conventions.md for artefact boundaries.

Artefact

Default path: .agency/architecture/solution.md — arc42-lite architecture (stub or full).

Path resolution

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

Stage (write mode)

Stage	When	Sections
`stub`	Phase 0	§1–§2 only; §3–11 scaffolded
`full`	Phase 2+	All eleven sections

Gotchas

Per-epic files/APIs → cite from .agency/work/{epic}/design.md, don't duplicate full specs.
Story-level Gherkin → tasks.md, not solution.
Closed ADRs → ADR-NNNN-*.md; proposals stay in register only.

Supporting files

assets/solution.template.md

Related skills

product, backlog, tasks, design, adr

Router

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

write — --stage stub|full.