docs: add issue routing guidance and contributor-guide-aware routing to fusion-issue-authoring (#112)

* docs: add issue routing guidance and contributor-guide-aware routing to fusion-issue-authoring

* docs: exclude security vulnerabilities from fusion-issue-authoring guidance

* docs: add security vulnerability disclosure reminder to issues section

* docs: fix link to issue tracker for feature requests in issue authoring guidance

Author: odinr

.changeset/issue-authoring-routing-guidance.md

@@ -0,0 +1,8 @@
+---
+"fusion-issue-authoring": patch
+---
+
+Add contributor-guide-aware repository routing to issue authoring
+
+- SKILL.md Step 2: read active workspace `CONTRIBUTING.md` / `contribute/` for routing rules before asking the user
+- `references/instructions.md`: add Repository routing note pointing to SKILL.md Step 2 as authoritative flow

CONTRIBUTING.md

@@ -51,6 +51,12 @@ Before requesting review, make sure your PR is:
 
 If you are unsure about direction, open a draft PR early and ask for feedback.
 
+## Issues and feature requests
+
+Use the `fusion-issue-authoring` skill to draft and publish issues — it enforces draft-first review, correct routing, and consistent structure. See [Issue authoring guide](contribute/07-issue-authoring.md) for routing rules and usage.
+
+Do not report security vulnerabilities via GitHub issues or `fusion-issue-authoring`; always follow [SECURITY.md](SECURITY.md) and Equinor CSIRT guidance instead.
+
 ## Full contribution guide
 
 Use the full maintainer workflow in [contribute/README.md](contribute/README.md).

contribute/01-where-to-start.md

@@ -36,3 +36,5 @@
 ## Questions and uncertainty
 
 If naming, safety constraints, or ownership are unclear, open a draft PR early and document the open questions in the PR description.
+
+For issue routing and how to author issues, see [CONTRIBUTING.md](../CONTRIBUTING.md).

contribute/07-issue-authoring.md

@@ -0,0 +1,40 @@
+# Issue authoring
+
+All **non-security** issues related to this repository must be drafted and published using the **`fusion-issue-authoring`** skill.
+
+The skill enforces draft-first review, reads this repository's contributor guides to resolve the correct destination automatically, and walks through a confirm-before-publish gate — so no issue lands in the wrong tracker or goes out half-baked.
+
+> **Security vulnerabilities:** Do **not** use GitHub issues or the `fusion-issue-authoring` skill to report potential security issues. Instead, follow this repository's responsible disclosure process described in [`SECURITY.md`](../SECURITY.md).
+
+## Where issues go
+
+| Issue type | Repository |
+|---|---|
+| Bug, CI failure, tooling error, skill regression | [equinor/fusion-skills](https://github.com/equinor/fusion-skills/issues) |
+| Feature, user story, task, improvement | [equinor/fusion-core-tasks](https://github.com/equinor/fusion-core-tasks/issues) |
+
+## Install the skill
+
+If you don't have it installed, ask Copilot:
+
+> "find a skill for issue authoring"
+
+## How to use
+
+Just describe what you want — the skill classifies, templates, routes, and drafts:
+
+- "create an issue for X"
+- "draft a bug report"
+- "turn this into a task"
+- "update issue #123"
+
+## Why the skill, not a manual issue form?
+
+- Applies the right template (repository template or type-specific fallback).
+- Checks for duplicates before drafting.
+- Confirms routing against this repo's contributor guides — no wrong-tracker mistakes.
+- Enforces a confirm-before-publish gate — no accidental mutations.
+- Caches label and assignee lookups to minimize back-and-forth.
+- Ensures full issue references (`owner/repo#123`) and closing keywords are used consistently.
+
+Skipping the skill means skipping these gates.

contribute/README.md

@@ -22,3 +22,7 @@ Then follow this path:
 If your change touches automation in `scripts/`, read [Repository scripts and code rules](06-scripts-code-rules.md) before opening a PR.
 
 Why? Script changes can break CI, release flow, or both — and nobody enjoys surprise archaeology in pipeline logs.
+
+## Reporting issues or requesting features?
+
+Read [Issue authoring guide](07-issue-authoring.md) to learn which repo to use and how to draft issues with the `fusion-issue-authoring` skill.

skills/fusion-issue-authoring/SKILL.md

@@ -77,6 +77,8 @@ If ambiguous, ask only essential clarifying questions.
 ### Step 2 — Resolve repository and template
 
 - Resolve the destination repository before any mutation.
+- When no explicit repository is given, check the active workspace for contributor guides (`CONTRIBUTING.md`, `contribute/`) that define default issue routing by type. Apply any routing rules found there before asking the user.
+- If no routing guidance exists in the repo, ask explicitly where the issue should be created.
 - Template precedence:
   1. repository template (`.github/ISSUE_TEMPLATE/`)
   2. specialist fallback template

skills/fusion-issue-authoring/references/instructions.md

@@ -21,10 +21,14 @@ Goal: create clear GitHub issues fast, with draft-first review and safe mutation
 - Run sub-issue mutations only for relationships that actually changed.
 - If rate limits are hit, stop optional lookups and return a clear retry plan.
 
+## Repository routing
+
+Routing is repo-specific. When no explicit repository is given, read the active workspace's `CONTRIBUTING.md` and `contribute/` docs and apply any issue routing rules found there. See SKILL.md Step 2 for the authoritative flow. Never hardcode destinations in this skill.
+
 ## Workflow
 
 1. Classify issue type (`Bug`, `Feature`, `User Story`, `Task`).
-2. Resolve destination repository.
+2. Resolve destination repository (apply contributor guide routing when in the active workspace context).
 3. Check template source in order:
 	- repository template (`.github/ISSUE_TEMPLATE/`)
 	- specialist fallback template