openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
- License 许可
- MIT
- 所属仓库
- Vortex375/seraph
- 最近更新
- 2026-11-08
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- gdpr-codes-of-conduct
- license
- Apache-2.0
- metadata
- { "tags": "gdpr, codes-of-conduct, article-40, article-41, monitoring-body, industry-code", "author": "mukul975", "domain": "privacy", "version": "1.0", "subdomain": "gdpr-compliance" }
- description
- Guides development of GDPR Article 40-41 codes of conduct for industry sectors including drafting, submission, and monitoring body requirements. Activate when creating industry codes or establishing monitoring bodies. Keywords: codes of conduct, Article 40, Article 41, monitoring body, industry code.
02 资源文件 4
- 资产文件assets/template.md1.7 KB
- 参考文档references/standards.md1.4 KB
- 参考文档references/workflows.md1.5 KB
- 脚本scripts/process.py3.1 KB
03 SKILL.md 正文
Developing Codes of Conduct
Overview
Articles 40-41 provide a framework for associations representing categories of controllers or processors to prepare codes of conduct. Codes specify the application of GDPR to specific sectors, provide practical guidance, and serve as an accountability tool under Art. 24(3).
Implementation Approach
Phase 1: Assessment
- Review current state against applicable GDPR articles.
- Identify gaps between current practices and requirements.
- Classify gaps by severity and regulatory risk.
- Document the assessment with evidence references.
Phase 2: Design
- Design measures to address identified gaps.
- Align measures with organisational capacity and risk appetite.
- Obtain DPO and stakeholder review of proposed measures.
- Create implementation timeline with milestones.
Phase 3: Implementation
- Execute the implementation plan according to priority.
- Document all measures implemented with evidence.
- Train relevant staff on new procedures and requirements.
- Validate implementation through testing or review.
Phase 4: Maintenance
- Schedule periodic reviews (minimum annual).
- Monitor for regulatory changes affecting the scope.
- Update measures in response to audit findings or incidents.
- Report on compliance status to the governance structure.
04 同仓库更多 Skills
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
wizard
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
wait-what
Stop. That last message did not land: re-pitch it.
triage
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
to-tickets
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).