atlas-crew-taskslisted

Use when filing, updating, sequencing, or querying tasks in any atlas-crew repo (Facet + the Atlas Crew Security repos: Apparatus, Chimera, Crucible, Synapse, Bridge). These repos track work in GitHub Issues on Projects v2 boards, NOT backlog.md. Covers the two boards, the Type/Area/Status field model, cross-repo Initiative grouping, gh seq execution ordering, and the non-obvious gh/GraphQL mechanics for setting issue types and project fields. Trigger on: file an issue, create a task, set priority/type/area/status, add to board, what should I work on next, execution order, sequencing, blocked-by, milestone, where does this task go.
NickCrew/Claude-Cortex · ★ 15 · AI & Automation · score 74

Install: claude install-skill NickCrew/Claude-Cortex

# Atlas Crew Task Tracking Work for these repos lives in **GitHub Issues** on **Projects v2** boards, not backlog.md. (A repo's `backlog/` directory is a frozen archive of completed pre-migration work — read-only.) ## The two boards | Board | Repos | URL | | --- | --- | --- | | **#8 Atlas Crew Security** (shared) | Apparatus, Chimera, Crucible, Synapse, Bridge | `https://github.com/orgs/atlas-crew/projects/8` | | **#9 Facet** (standalone) | Facet | `https://github.com/orgs/atlas-crew/projects/9` | Both are **org-owned** by `atlas-crew`. Always pass `--owner atlas-crew`. ## Classification model (three orthogonal axes) Keep these separate — do not encode type or area as a label. - **Type** → GitHub **Issue Type** (org-owned, shared by every repo): `Feature`, `Bug`, `Task`, `Chore` (refactor/tech-debt/maintenance), `Spike` (time-boxed investigation). - **Area** → an **Area** single-select project field. *Facet #9 only* so far (Identity, Pipeline, Prep, Letters, Research, Build/Resume, Debrief, AI/Proxy, UI/Design System, Persistence, Testing/Infra, Docs, Cross-cutting). Board #8 has no Area field yet. - **Concern** → **labels**: `accessibility`, `security`, `ux`, `cross-cutting`, `testing`, `documentation`, `playwright`, plus GitHub/dependabot conventions. **Cross-repo grouping** is the **Initiative** single-select on board #8 (e.g. "Platform Hardening", "Vuln Content") — use it for milestones that span ACS repos. Within a single repo, use native GitHub **mil