skills/skills/mappa-vitya-project-discipline/README.md

mappa-vitya-project-discipline

Vitya-flavored cross-project discipline policy skill for a mappa knowledge zone. Codifies the five work rules (project-canon via mappa, master-only, semver, push) PLUS four mappa-canon rules (rg-only search, live-verify after reload, knowledge-first, durable-knowledge-to-wiki).

When it triggers

• Session start — when AGENTS.md contains the line follow mappa-vitya project discipline (inserted by mappa-bootstrap, which selects the project's methodology flavor).
• In-chat — when the user says "use project discipline", "соблюди дисциплину", "проектные правила", "follow project discipline", or close variants.

The rules

1. Project canon is a mappa wiki entity, not files. Read the project's AGENTS entity (wiki_get(project,'AGENTS')), NOT .wiki/CLAUDE.md / .tasks/ (file channel closed). Before any wiki work — run mappa-knowledge first.
2. Master-only. All work on master (or main). No feature branches without explicit user approval.
3. Semver discipline. Bump version: in SKILL.md / package.json / pyproject.toml on every edit per MAJOR / MINOR / PATCH; record in commit message; rebuild dist/ artifacts after.
4. Push freely by default. No confirmation needed for push; a local push gate (push gate: ask in AGENTS entity, or explicit operator word) overrides per project. Force / delete / non-ff push always asks.
5. Transit-zone / brainstorm workspaces (mappa channel). Brainstorm artifacts go to a mappa brainstorm entity, not .brainstorm/*.md. Only promote to a wiki concept when the user explicitly directs.

Mappa-canon rules

• Rule G — rg-only search. Never walk node_modules/dist/build with grep -r/find/ag/ack. Use rg (gitignore-aware); never rg --no-ignore.
• Rule K — knowledge-first. Run mappa-knowledge before any wiki work.
• Rule L — live-verify after reload. Infra changes verified in a live interactive session, not headless.
• Rule D — durable knowledge to mappa wiki. Never memory/ / local files; go to a mappa wiki entity.

Prerequisites

• mappa MCP server available (mcp__mappa__*) to read the canon.
• mappa-knowledge skill installed.
• Methodology flavor selected by mappa-bootstrap (the source of the follow mappa-vitya project discipline trigger line).

Related

• mappa-bootstrap — picks the methodology flavor per project and inserts the trigger line.
• project-bootstrap — writes the project scaffold (removed the legacy follow project discipline trigger; the generic skill was replaced by the per-flavor mappa-vitya-project-discipline).
• mappa-vitya-brainstorming — the brainstorm METHODOLOGY for a mappa zone.