These are Paperclip platform mechanics already covered by the
Paperclip skill. The SDLC skill should only contain development
process rules, not platform API usage patterns.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Replace the 5-stage pipeline (CI→UAT→QA→CTO→CEO) with a three-branch
promotion chain: dev (engineer self-merge) → uat (QA gates) → main
(UAT gates). Removes CTO review stage, CEO merge bottleneck, and SLA
timelines. Each gate owner has merge authority.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
SLA timelines are meaningless to agents operating in heartbeats.
Removed the 48-hour PR review SLA from SKILL.md and the SLA
gantt chart from sdlc-diagram.md.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
- Restore .github/workflows/ci.yaml that was deleted in April cleanup
- Add .markdownlint.yaml with relaxed rules for skill files
- Fix MD040 error in skills/sdlc/SKILL.md (add language to code block)
- Allows line lengths > 80, emphasis-as-headings, compact tables
Fixes CI failures on 'Merge POLICIES.md content into agent instruction bundles' commit.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
SDLC skill (250 → ~127 lines):
- Remove Hugh-exclusive .github/workflows/ language; engineers share access
- Condense 48-hour SLA from 38 to 8 lines
- Replace verbose 5-stage pipeline description with compact diagrams
- Condense handoff protocol from 17 to 5 lines
- Remove status transition rules table (redundant with handoff protocol)
- Remove agent roster (agents have UUIDs in their own AGENTS.md)
- Remove work distribution section (redundant with agent instructions)
Coding-standards skill:
- Add SemVer, ArtifactHub distribution, ghcr.io registry rules
- Add Renovate/Dependabot, no-package-mirrors, npm-audit rules
- These were previously only in individual AGENTS.md files
Part of PRI-1094 — agent and process review.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Replace dismissal-threat framing with operational consequences:
- 24h: public visibility + status flag
- 48h: merge queue block + escalation
- 72h+: blocks release if critical-path
- Exceptions: documented hand-off, not absolute prohibition
This makes the enforcement mechanism work for agents (visibility/process blocking)
rather than humans (dismissal threats), matching actual organizational incentives.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Chris Farhood