/standards-discover

name: standards-discover
description: Discover coding standards from project configuration files, code patterns, documentation, and external sources (PRs, CI/CD)

Standards Discovery Skill

Analyzes multiple project sources in parallel to discover coding standards, conventions, and best practices. Aggregates findings with confidence scoring, presents for user approval, and applies approved standards via `docs-manager` skill.

Core Principles

1. **Parallel Execution**: Launch discovery subagents concurrently for speed (~45-60s vs ~2-4min sequential) 2. **Evidence-Based**: Every finding must cite specific files, line counts, or config rules as evidence 3. **Confidence Scoring**: Multi-factor confidence based on source count, consistency, and explicitness 4. **Deduplication**: Same standard found across sources merges into single finding with combined evidence 5. **Graceful Degradation**: Skip unavailable sources (no gh CLI, no docs) without failing entire workflow

---

Input Parameters

| Parameter | Default | Description | |-----------|---------|-------------| | `--scope` | `full` | Discovery scope: `full`, `quick`, or any category name (baseline: `global`, `frontend`, `backend`, `testing`; custom categories also supported) | | `--confidence` | `60` | Minimum confidence threshold (0-100) for displaying findings | | `--auto-apply` | `false` | Auto-apply standards with confidence >= 90% without asking | | `--skip-external` | `false` | Skip GitHub PR analysis and CI/CD sources | | `--pr-count` | `20` | Number of recent merged PRs to analyze |

**Scope determines which phases run:**

| Scope | Config (P1) | Code (P2) | Docs (P3) | External (P4) | |-------|-------------|-----------|-----------|----------------| | `full` | Yes | Yes | Yes | Yes | | `global` | Yes | Yes (limited) | Yes | Yes | | `frontend` | FE configs | FE files | Yes | Yes | | `backend` | BE configs | BE files | Yes | Yes | | `testing` | Test configs | Test files | Yes | Yes | | `quick` | Yes | No | No | No | | `[custom]` | Relevant configs | Filtered files | Yes | Yes |

Custom scope values are matched against existing `.maister/docs/standards/*/` directories and filter analysis to relevant files.

---

Phase Configuration

| Phase | Subject | activeForm | |-------|---------|------------| | 1 | Plan discovery scope | Planning discovery scope | | 2 | Analyze configuration files | Analyzing configuration files | | 3 | Mine code patterns | Mining code patterns | | 4 | Extract documentation standards | Extracting documentation standards | | 5 | Analyze external sources | Analyzing external sources | | 6 | Aggregate & deduplicate findings | Aggregating findings | | 7 | Review findings with user | Reviewing findings | | 8 | Apply approved standards | Applying standards | | 9 | Generate summary report | Generating summary |

**Task Tracking**: At start of Phase 1, use `TaskCreate` for all phases above (pending). Set dependencies: Phases 2-5 blocked by Phase 1 (they run in parallel after planning). Phase 6 blocked by Phases 2-5. Phases 7-9 sequential. At each phase start: `TaskUpdate` to `in_progress`. At each phase end: `TaskUpdate` to `completed`. For phases skipped due to scope (e.g., Phases 3-4 when `--scope=quick`), mark `completed` with `metadata: {skipped: true, reason: "scope=quick"}`.

---

Execution Workflow

Phase 1: Planning & Initialization

1. **Parse options** from command arguments 2. **Check prerequisites**: Verify `.maister/docs/` exists. If not, offer to run `/maister-init` first 3. **Read existing standards** from `.maister/docs/INDEX.md` to identify updates vs creates and avoid duplicates 4. **Display discovery plan** showing scope, sources, and estimated time 5. **Get user confirmation** via ask_user before proceeding

---

Phase 2-5: Parallel Discovery

Launch all applicable subagents in one message so they run in parallel.

**Step 1: Determine which phases to run** based on scope and flags.

**Step 1.5: Create temp output directory** — Run `mktemp -d` via Bash to create a unique temp directory for this invocation. Store the path (e.g., `/tmp/abc123`). Each subagent will write its results to a dedicated file in this directory: `{tmpdir}/config.yml`, `{tmpdir}/code.yml`, `{tmpdir}/docs.yml`, `{tmpdir}/external.yml`.

**Step 2: Read prompt templates**

Read the template for each phase you will run — they define the YAML output schema the aggregation step depends on:

| Phase | Condition | Read This File | |-------|-----------|----------------| | 2: Config Analysis | Always | `references/config-analyzer-prompt.md` | | 3: Code Patterns | scope != `quick` | `references/code-pattern-prompt.md` | | 4: Documentation | scope != `quick` | `references/docs-extractor-prompt.md` | | 5: External Sources | `--skip-external` not set | `references/external-analyzer-prompt.md` |

**Step 3: Adapt templates** — Replace `[scope]`, `[confidence]`, and other placeholders with actual values. Replace the `[output_file]` placeholder in each template with the actual temp file path for that phase (e.g., `{tmpdir}/config.yml`).

**Step 4: Launch subagents in parallel** — Use the Task tool with `subagent_type: general-purpose` for each phase.

**Step 5: Wait** for ALL subagents to complete, then read each temp file using the Read tool to collect findings.

**Step 6: Display progress** — Show count of findings per phase.

---

Phase 6: Aggregation & Deduplication

**Read** `references/aggregation-strategy.md` for confidence scoring methodology.

1. **Combine** all findings from Phases 2-5 2. **Deduplicate** by grouping on `category + standard_name` — merge evidence and sources 3. **Calculate final confidence** using multi-factor scoring from the reference 4. **Detect conflicts** — flag contradictory standards (e.g., ESLint says semicolons, Prettier says no) 5. **Categorize** into High (>= 80%), Medium (60-79%), Low (< 60%) 6. **Filter** by `--confidence` threshold

Display aggregation summary: total raw fi