GrinRus

Aggregates shared runtime navigation and cross-skill ownership links. Use when resolving shared runtime entrypoints or ownership boundaries. Do not use when the request belongs to `aidd-policy` output/question rules or `status` summary reporting.

Owns shared DocIO runtime for markdown slicing/patching, actions validation/apply, and context-map expansion. Use when stage skills need canonical DocIO operations. Do not use when the request primarily belongs to `aidd-flow-state` lifecycle updates or `aidd-core` ownership routing.

Owns shared flow/state runtime for stage state, progress/tasklist, and stage-result lifecycle. Use when orchestration needs canonical active-stage, progress, tasklist, or stage-result commands. Do not use when the request is about `aidd-docio` action patch mechanics or `status` read-only summaries.

Initializes AIDD workspace scaffolding for the current project. Use when bootstrapping canonical `aidd/` templates and project-owned test execution contract in `aidd/config/gates.json`. Do not use when the request is to start feature ideation (`idea-new`) or to inspect existing ticket progress (`status`).

Enforces loop-mode discipline for implement/review/qa (packs, scope, no questions). Use when loop stages require bounded scope and retry policy. Do not use when direct stage execution belongs to `implement`, `review`, or `qa` stage skills.

Owns shared observability/runtime reporting for diagnostics, inventory, identifiers, logs, and DAG export. Use when deterministic diagnostics or inventory exports are required. Do not use when request scope is `status` stage summaries or `aidd-core` runtime ownership mapping.

Owns shared RLM evidence workflow for subagents (slice, build, verify, finalize, pack). Use when preload roles require canonical RLM evidence operations. Do not use when the request is stage-local research execution in `researcher` or stage handoff-only guidance in `aidd-stage-research`.

Bootstraps a new feature ticket by setting active context, deriving `slug_hint`, and preparing PRD questions. Use when the idea stage starts for a new ticket. Do not use when the request is to refresh research artifacts (`researcher`) or draft implementation plans (`plan-new`).

Prepare, publish, verify, and record AIDD Python package releases through this repository's release/v<version> branch and GitHub Release published-event flow; use when cutting a new prerelease or release, running release dry-runs, checking PyPI/pipx/uv tool evidence, or performing post-release version-bump follow-up.

Run or prepare a manual full-flow live end-to-end scenario against a public GitHub repository with repository pinning, authored task selection, execution evidence capture, and manual post-run quality reporting.

Run harness and eval scenarios for ai_driven_dev_v2, validate document-first stage outputs, preserve runtime logs, analyze failures, and produce durable audit artifacts for deterministic and manual-live lanes.

Select, split, create, promote, and close roadmap tasks while keeping `roadmap.md` and `backlog.md` synchronized.

Map a task to the right AIDD docs, modules, checks, and scenario assets before making changes.

Analyze runtime and adapter logs to identify the first decisive failure signal and classify it correctly.

Make a safe change to a stage or document contract by updating contracts, validators, prompts, and scenarios together.

Turn a coarse roadmap item into reviewable local tasks with one output, one dominant touched area, and one main verification signal.

Use when you need to choose a delivery slice, derive local tasks, split a slice, or verify that a change still matches the current roadmap.

Use when you need to run or assess AOR live E2E profiles through the black-box step journal.

Use when you need to prepare, review, or update a live E2E rehearsal profile for AOR.

Use when preparing, reviewing, validating, or publishing an AOR npm CLI alpha release for @grinrus/aor.

Use when a feature or flow change adds fields, changes packets, changes reports, or affects routes, wrappers, policies, or APIs.

Use when you need to decide where a change belongs in the AOR repository or which docs, examples, and modules must change together.

Use when you need to verify that a change maps to supported user stories or when you need to check that a workflow still closes the intended role-based outcome.

Используй для trusted-machine pre-release live E2E gate, canonical 5-profile taxonomy (`regres fast|long`, `release fast|long|full`) и дополнительных non-release smoke/diagnostic прогонов поверх baseline/parallel-default sweeps.

Используй, когда изменения кода требуют обновления документации. Держит README/docs/ARCHITECTURE/docs/STAKEHOLDER_DOC в согласованном виде.

Используй при изменении схем/контрактов (TaskResult, форматы модели). Гарантирует синхронность docs/валидаторов/фикстур.

Используй при старте новой фичи. Превращает slice backlog в минимальный, тестируемый план реализации.

Используй при изменении логики извлечения/модели. Добавляет/обновляет фикстуры и golden outputs для защиты от регрессий.