تشغيل أي مهارة في Manus بنقرة واحدة

adr

النجوم٢

التفرعات٠

آخر تحديث١٩ يوليو ٢٠٢٦ في ١٢:٠٥

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.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

carinyaparc

carinyaparc/skills

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

مستكشف الملفات

6 ملفات

SKILL.md

readonly

name	adr
description	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.
license	MIT
allowed-tools	Read Write Glob Grep
argument-hint	<mode: plan\|write\|review> [epic\|target] [flags]
metadata	{"author":"Carinya Parc","version":"1.0","owner":"architecture","work_shape":"authoring","output_class":"delivery-artefact"}

ADR

Paths

Artefact	Default path
Register	`docs/architecture/decisions/register.md`
ADR document	`docs/architecture/decisions/ADR-{NUMBER}-{short-title}.md`

Path resolution

If the user names a different directory or file path in their request, use it for read/write instead of the defaults. Keep ADR-#### numbering sequential within the register the user targets.

Supporting files

Router

Mode: plan, write, or review.
Resolve paths (default or user override). plan takes an optional epic: adr plan <epic> harvests decisions already made in docs/work/{epic}/design.md and triages them into the register. Without an epic it surveys product.md and solution.md for decisions still to be made.
prompts/plan.prompt.md | prompts/write.prompt.md | prompts/review.prompt.md.

المزيد من هذا المستودع

نفس المستودع

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

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

docs-review

carinyaparc/skills

Use when the user wants a set of documents reviewed — a docs folder, a wiki, a handbook, a repo's markdown, or any collection of written material. Checks that each document is well written and well structured, that boundaries between documents are clear with no duplication, and that the set is consistent and cohesive. Triggers on "review the docs", "are these docs any good", "is our documentation consistent", "do these docs overlap", "audit the documentation". Works on any doc set in any format or tool. Read-only: produces a report and changes nothing. Do NOT use to write or amend a document, to review code (code-review), or to review rendered UI (ux-design-review).

2026-07-192

name	adr
description	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.
license	MIT
allowed-tools	Read Write Glob Grep
argument-hint	<mode: plan\|write\|review> [epic\|target] [flags]
metadata	{"author":"Carinya Parc","version":"1.0","owner":"architecture","work_shape":"authoring","output_class":"delivery-artefact"}

ADR

Paths

Artefact	Default path
Register	`docs/architecture/decisions/register.md`
ADR document	`docs/architecture/decisions/ADR-{NUMBER}-{short-title}.md`

Path resolution

If the user names a different directory or file path in their request, use it for read/write instead of the defaults. Keep ADR-#### numbering sequential within the register the user targets.

Supporting files

Router

Mode: plan, write, or review.
Resolve paths (default or user override). plan takes an optional epic: adr plan <epic> harvests decisions already made in docs/work/{epic}/design.md and triages them into the register. Without an epic it surveys product.md and solution.md for decisions still to be made.
prompts/plan.prompt.md | prompts/write.prompt.md | prompts/review.prompt.md.