القائمة
Enforces OpenSpec authoring conventions including metadata blocks, section ordering, requirement/scenario structure, and validation steps.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Automatically applies when designing multi-agent systems. Ensures proper tool schema design with Pydantic, agent state management, error handling for tool execution, and orchestration patterns.
Automatically applies when securing AI/LLM applications. Ensures prompt injection detection, PII redaction for AI contexts, output filtering, content moderation, and secure prompt handling.
Automatically applies when reviewing code. Ensures structured review checklist covering correctness, security, performance, maintainability, testing, and documentation.
Automatically applies when working with database migrations. Ensures proper Alembic patterns, upgrade/downgrade scripts, data migrations, rollback safety, and migration testing.
Automatically applies when managing Python dependencies. Ensures proper use of uv/Poetry, lock files, version constraints, conflict resolution, and dependency security.
Automatically applies when evaluating LLM performance. Ensures proper eval datasets, metrics computation, A/B testing, LLM-as-judge patterns, and experiment tracking.
| name | openspec-authoring |
| description | Enforces OpenSpec authoring conventions including metadata blocks, section ordering, requirement/scenario structure, and validation steps. |
| category | documentation |
Trigger Keywords: openspec, proposal, change-id, tasks.md, spec delta, requirement, scenario, validation, archive
Agent Integration: Used by spec-writer and planning agents when creating or updating OpenSpec proposals, tasks, and spec files.
Change ID, Status, Date, and Author near the top.# Spec: <Title> plus capability/status/related lines.change-id (e.g., add-doc-spec-writer-agent).## ADDED|MODIFIED|REMOVED Requirements → Scenarios per requirement with Given/When/Then.#### Scenario: block.openspec validate <change-id> --strict when available.openspec/specs/...).openspec/archive/.openspec archive <id> --skip-specs --yes only for tooling-only changes.