원클릭으로 Manus에서 모든 스킬 실행

wiki-first-query

스타6

포크4

업데이트2026년 7월 21일 14:48

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 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

gosha70

gosha70/code-copilot-team

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Wiki-First Query Convention

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.

The convention

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:

Read knowledge/wiki/index.md (repo-relative path) to find pages relevant to your topic.
Follow the links into concepts/, workflows/, incidents/, decisions/, playbooks/, or glossary/ as relevant.
Treat what you find there as the project's current best understanding. Each page lists its sources in frontmatter; if you need deeper detail, follow those citations.

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.

When the wiki is silent or stale

If the wiki has nothing on the topic, or what it has is clearly out of date with the current code:

Do the raw research yourself.
If what you learn is reusable beyond this session, propose a promotion by following the procedure in knowledge/wiki/workflows/promote-lesson-to-wiki.md (repo-relative path).
Do not silently fix wiki content as a side effect of other work — wiki edits are intentional, single-purpose changes.

In Claude Code, the /promote-lesson <description> slash command runs the promotion workflow on your behalf. Other adapters can follow the workflow document directly.

What this convention does NOT do

It does not require you to read every wiki page on every invocation. Read the index, then drill into what is relevant.
It does not replace the SDD spec workflow. Specs still own feature requirements; the wiki holds knowledge that outlives any one feature.
It does not replace session memory. Memory holds session ephemera; the wiki holds what survives.

이 저장소의 다른 Skills

같은 저장소

agent-team-protocol

gosha70/code-copilot-team

Multi-agent delegation rules, three-phase workflow (Plan/Build/Review), model selection, collaboration gates, and Ralph Loop integration.

2026-07-216

auto-build-loop

gosha70/code-copilot-team

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.

2026-07-216

clarification-protocol

gosha70/code-copilot-team

When and how to ask clarifying questions before implementing. Data model review gate and ambiguity resolution rules.

2026-07-216

coding-standards

gosha70/code-copilot-team

Quality gates, prohibited patterns, verification discipline, and self-audit rules for all code generation and review sessions.

2026-07-216

copilot-conventions

gosha70/code-copilot-team

Cross-copilot portable conventions: read before write, minimal changes, git discipline, project structure, and priority rules.

2026-07-216

gosha70/code-copilot-team

2026-07-216

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.

Wiki-First Query Convention

The convention

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:

Read knowledge/wiki/index.md (repo-relative path) to find pages relevant to your topic.
Follow the links into concepts/, workflows/, incidents/, decisions/, playbooks/, or glossary/ as relevant.
Treat what you find there as the project's current best understanding. Each page lists its sources in frontmatter; if you need deeper detail, follow those citations.

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.

When the wiki is silent or stale

If the wiki has nothing on the topic, or what it has is clearly out of date with the current code:

Do the raw research yourself.
If what you learn is reusable beyond this session, propose a promotion by following the procedure in knowledge/wiki/workflows/promote-lesson-to-wiki.md (repo-relative path).
Do not silently fix wiki content as a side effect of other work — wiki edits are intentional, single-purpose changes.

In Claude Code, the /promote-lesson <description> slash command runs the promotion workflow on your behalf. Other adapters can follow the workflow document directly.

What this convention does NOT do

It does not require you to read every wiki page on every invocation. Read the index, then drill into what is relevant.
It does not replace the SDD spec workflow. Specs still own feature requirements; the wiki holds knowledge that outlives any one feature.
It does not replace session memory. Memory holds session ephemera; the wiki holds what survives.