project-features

Installation
SKILL.md

Filing and triaging new-feature issues

A new-feature issue says "this web platform feature needs guidance." It comes before use cases (see the project-use-cases skill), and automation depends on it:

  • ATL routing: src/ci/atl-triage.ts assigns an ATL based on the issue's labels and its web-feature ID.
  • Use case tracking: src/ci/sync-use-cases.ts (called "the sync" below, run by the guide-sync workflow) matches use-case issues to the feature issue by ID. It also writes the use case checklist into the issue body, sets the project status, and closes the issue when every linked use case has complete guidance and expectations.
  • Priority: the feature issue's priority label and milestone are copied to its use-case issues.
  • Coverage: guidance coverage is measured by whether a feature's web-feature ID appears in a published guide.

Most triage problems come from one of five mistakes: using the template for a general request, filing a launch that isn't developer-facing, filing an incremental change as a new feature, filing a duplicate, or giving the issue the wrong ID. This skill covers each one.

Always confirm with the user before you post a comment, edit an issue body, change labels, set a status, or close an issue.

Step 1: Decide whether it qualifies

Work through these questions in order. Stop at the first one that settles it.

Is it about a specific web platform feature?

Installs
44
GitHub Stars
9.0K
First Seen
Oct 31, 2026