Pattern port plan

SDMCC Pattern Port Plan

Port decisions, inventory, safety boundaries, and validation plan for borrowed ClawdMarks-style patterns.

SDMCC ClawdMarks Pattern Port Plan

This plan covers DIF-80, DIF-81, and DIF-82 for the SDMCC Agent Skills repository. It uses the iDPCC handoff as source-history context and adapts the ClawdMarks patterns only where they fit SDMCC governance.

Confirmed Repository

Canonical repo: https://dev.azure.com/difzses/SDMCC/_git/SDMCC-Agent-Skills
Working path for this change: /Users/BrianM/SDMCC-Agent-Skills-DIF-80-82
Branch: codex/DIF-80-82-sdmcc-skills-patterns
Linear project: SDMCC - General Contract Work
Tickets: DIF-80, DIF-81, DIF-82

The original worktree at /Users/BrianM/SDMCC-Agent-Skills had unrelated local changes on codex/azure-pbi-task-assignees, so this branch was created in a separate worktree from origin/main.

Source Material Reviewed

SDMCC AGENTS.md and CONTRIBUTING.md.
iDPCC source-history handoff at /Users/BrianM/iDPCC-Agent-Skills/docs/sdmcc-sync-handoff.md.
Local ClawdMarks repo at /Users/BrianM/clawdmarks.

The iDPCC handoff is useful for sync order and safety checks. ClawdMarks is useful for the audience split, copyable agent onboarding, field-report vocabulary, and operational sorting ideas. Neither source should contribute iDPCC URLs, iDPCC AWS names, ClawdMarks branding, public-review semantics, local generated state, or credentials.

SDMCC Inventory

Current SDMCC assets already include the shared Skills platform parity set:

Skill library: skills/_template/, skills/azure-devops-pbi/, skills/meeting-to-backlog-brief/, skills/qa-test-plan-builder/, skills/release-readiness-review/, and skills/skill-review-readiness/.
Install and skill setup docs: docs/installing-agent-skills.md, docs/new-user-setup.md, docs/coworker-azure-devops-cli-ssl-note.md, and setup scripts under scripts/.
Analytics and governance docs: docs/agent-analytics-contract.md, docs/analytics-data-governance.md, docs/skills-metric-dictionary.md, docs/skills-architecture.md, docs/skills-collector.md, docs/pbi-agent-analytics-dashboard.md, docs/skills-status.md, and docs/skills-operations.md.
Platform code: site/, server.mjs, scripts/agent-analytics-*, scripts/*dashboard*, scripts/*collector*, scripts/*recommendation*, lambda/, and fixtures/agent-analytics/.
Infrastructure scaffold: infra/skills/, scripts/deploy-skills-aws.sh, scripts/build-skills-lambda-artifacts.mjs, scripts/write-skills-site-config.mjs, and scripts/validate-skills-infra.mjs.

This means the next port does not need another broad iDPCC platform copy. It should be a narrow SDMCC feature update on top of the existing app and docs.

Port Decisions

Pattern	SDMCC decision	Implementation area
Human/agent audience split	Keep the idea, rename it for SDMCC as Human Mode and Agent Mode. Human Mode explains governance and status. Agent Mode gives concise operational steps an agent can copy.	`site/index.html`, `site/app.js`, `site/styles.css`, `docs/agent-mode-instructions.md`
Copyable agent instructions	Keep copyable prompts and commands, but point them only at SDMCC repo URLs, SDMCC docs, and `skills/azure-devops-pbi/references/project-profile.md`.	`README.md`, `docs/installing-agent-skills.md`, `docs/agent-mode-instructions.md`, library UI
Field reports	Treat reports as signed-in operational evidence, not public social reviews. Store strict categories, rating, short sanitized comment, timestamps, and submitter authorization context.	`docs/skill-field-reports.md`, `scripts/skill-feedback-lib.mjs`, `site/app.js`
Operational sorting	Add sorting that can be supported by current data: Needs Review, Recently Updated, Production Ready, and Most Reported Issues. Plan Most Installed/Used only after install/usage events are stored.	`site/index.html`, `site/app.js`, docs
Source branding	Do not copy ClawdMarks name, imagery, public leaderboard, public reviews, public agent profile pages, API key model, or User-Agent write gate.	Not ported

Safety Boundaries

Do not copy secrets, PATs, passwords, .env*, .mcp.json, local auth files, raw deployment logs, generated local app state, raw exports, meeting recordings, transcripts, screenshots, or credentials.
Do not copy iDPCC board rules, Linear routing, AWS account IDs, hosted zones, CloudFront/API URLs, Cognito domains, stack names, or secret names into SDMCC unless they are rewritten and verified as SDMCC values.
Do not infer SDMCC board-field requirements from iDPCC.
Do not make field reports a public rating system; keep them as governed operational evidence for the Skills workspace.

SDMCC Unknowns

Production Skills hostname and production AWS account are not approved in this repo.
Collector and recommendation schedules remain disabled until the SDMCC PAT secret is approved and installed in Secrets Manager.
"Most Installed/Used" sorting needs a governed install/usage event source. The current repo has install requests and feedback reports, but no reliable install-completion or use-count store.
Field-report retention enforcement should be tied to the existing dashboard data retention work before production launch.

Validation Plan

Run the repository checks that match the implementation:

npm run site:check
rg -n "iDPCC|idpcc|ClawdMarks|clawdmarks|ceirr-network|skillz/idpcc|852507783007|643366142385|26hw3vgb05|lxrakkinvl" README.md docs site scripts skills infra fixtures lambda

Expected search results are limited to this plan's intentional source-history references. If new generated documentation mirrors those references, it must be visibly labeled as source-history context.