This skill should be used when creating RACI charts, mapping accountability by activity, resolving accountability gaps, or producing the Role-Responsibility Map artefact. Triggers when entering Phase 2 (Architecture) or Phase 3 (Discovery), or when team structure changes during delivery.
From agile-lifecyclenpx claudepluginhub nsalvacao/nsalvacao-claude-code-plugins --plugin agile-lifecycleThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Configures VPN and dedicated connections like Direct Connect, ExpressRoute, Interconnect for secure on-premises to AWS, Azure, GCP, OCI hybrid networking.
Clarity about who is responsible, accountable, consulted, and informed for each lifecycle activity prevents decisions from stalling, artefacts from being orphaned, and escalation paths from being unclear. This skill produces RACI charts per phase, maps accountability to named roles, and generates the Role-Responsibility Map — a mandatory Phase 2 artefact. It is maintained throughout all phases as team structure evolves.
List all roles participating in the project. Roles, not individuals — the RACI must remain valid when people change. Reference references/role-accountability-model.md for standard role definitions in this framework. Common roles:
For each role, record: name of role, current person filling it (for the project), and phase entry/exit date if temporary.
For each lifecycle phase in scope (determined by the tailoring profile from skills/lifecycle-tailoring/SKILL.md):
references/artefact-catalog.md and references/lifecycle-overview.md)Rules: every activity has exactly one A. Multiple R entries are allowed. C and I are optional. Activities with no A are accountability gaps — resolve before phase start.
An accountability gap exists when:
For each gap:
references/role-accountability-model.md defaultsCreate the Role-Responsibility Map as a project artefact:
Add the document to the Phase 2 evidence index.
The RACI is only useful if the team knows it:
The Role-Responsibility Map is a living document:
references/role-accountability-model.md — Standard role definitions, default RACI patterns, accountability modelreferences/lifecycle-overview.md — Phase activity lists used as RACI input rowsreferences/artefact-catalog.md — Artefacts that require an owner (R and A assignment)