القائمة
Wiki-first query convention: consult knowledge/wiki/index.md and the linked pages BEFORE re-reading raw sources for a project topic. The wiki is the canonical project memory layer.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Multi-agent delegation rules, three-phase workflow (Plan/Build/Review), model selection, collaboration gates, and Ralph Loop integration.
Autonomous build driver after SDD spec approval: phase-scoped headless build sessions, driver-owned commits, cross-provider review gates, milestone pauses, and fail-closed escalation — under explicit opt-in autonomy profiles.
When and how to ask clarifying questions before implementing. Data model review gate and ambiguity resolution rules.
Quality gates, prohibited patterns, verification discipline, and self-audit rules for all code generation and review sessions.
Cross-copilot portable conventions: read before write, minimal changes, git discipline, project structure, and priority rules.
Copyright header rules for generated source files. Applies the company name from providers.toml to new files.
| name | wiki-first-query |
| description | Wiki-first query convention: consult knowledge/wiki/index.md and the linked pages BEFORE re-reading raw sources for a project topic. The wiki is the canonical project memory layer. |
This project maintains a curated knowledge layer at
knowledge/wiki/. It is the canonical home for durable project
knowledge — concepts, workflows, incidents, decisions, playbooks,
glossary entries, and known open questions. Every page is cited
back to a raw source.
When you start work on a topic that touches this project's domain (SDD workflow, peer review, adapter generation, agent safety, shape-up cycles, etc.), consult the wiki first:
knowledge/wiki/index.md (repo-relative path) to find
pages relevant to your topic.concepts/, workflows/, incidents/,
decisions/, playbooks/, or glossary/ as relevant.Only after consulting the wiki should you fall back to raw sources (specs, issues, PRs, code) for the same topic. The wiki exists so that you do not re-discover the same context every session.
If the wiki has nothing on the topic, or what it has is clearly out of date with the current code:
knowledge/wiki/workflows/promote-lesson-to-wiki.md
(repo-relative path).In Claude Code, the /promote-lesson <description> slash command
runs the promotion workflow on your behalf. Other adapters can
follow the workflow document directly.