메뉴
Human-facing project-management hub for the Linear Method ontology, conventions, and the workspace safety gate. Load when reasoning about project/issue structure, Linear conventions, or how OpenSpec, beads, and GitHub relate as PM layers.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Index curated reference corpora into a searchable knowledge graph via the cognee engine, then query it to ground technical writing, review, and analysis. Use when ingesting reference documents into named datasets or retrieving grounding context for tasks like drafting or reviewing a manuscript. A reference-knowledge index, explicitly not agent session memory.
Nix development conventions for flakes, derivations, modules, and code style. Use when authoring flake.nix files, writing derivations or builders, designing NixOS/nix-darwin/home-manager modules, or following nix formatting and naming conventions. For check architecture and CI integration, see preferences-nix-checks-architecture and preferences-nix-ci-cd-integration.
Approximately-verifiable, refinement-driven development for type-driven domain-driven design. Use when modeling a domain as a dependently-typed Lean 4 specification, refining/lowering it to a Rust implementation, lifting the implementation back via Charon and Aeneas to check spec<->implementation correspondence (translation validation) — mechanically when tractable, otherwise via differential testing or LLM comparison — or when generating and diffing type-system diagrams of the model and implementation to track their evolution. Mechanical on-the-nose proof is the precise ideal, not a requirement; its absence is not a failure of the method.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Algebraic data type patterns including sum types, product types, and pattern matching across languages. Load when designing type hierarchies or working with discriminated unions.
Algebraic laws including functor/monad laws and property-based testing strategies. Load when verifying algebraic properties or writing property tests.
| name | project-management |
| description | Human-facing project-management hub for the Linear Method ontology, conventions, and the workspace safety gate. Load when reasoning about project/issue structure, Linear conventions, or how OpenSpec, beads, and GitHub relate as PM layers. |
This is the human-facing hub for how work is structured across the layers in this workspace. It documents the project-management model, conventions, and constraints; it does not itself mutate any tracker. Three other skills do the mechanical work and this hub routes to them by name rather than re-implementing them: the bundled linear-cli skill for raw Linear verbs, issues-beads for the local issue graph, and openspec-linear-sync for binding a Linear story to an OpenSpec change.
The spine of the model is the Linear Method ontology. Work decomposes as Initiative greater than Project greater than Milestone greater than Issue, and Cycles sit orthogonally as a time-boxed scheduling overlay rather than as a decomposition layer. An Initiative is cross-project strategy; a Project is a directional document plus an objective that links to (but does not duplicate) the specs that define correctness; a Milestone is a completion-oriented phase that leaves the system stable and forward-only; an Issue is the unit of both value and behavior.
The hub partitions into four sub-areas, each a separate concern a human consults independently. Linear holds the business "what" and the team-visible status surface, and carries the hardest constraint in this whole hub: the workspace safety gate. GitHub holds the pull-request, buildbot, and Mergify surface where a change's terminal artifact lands as one realization of the archived OpenSpec change. beads is an optional local fine-grained drill-down sublayer below the OpenSpec requirements document, load-bearing only in Manual mode. The method sub-area synthesizes the Linear Method and CCPM principles into the conventions that govern all of the above.
The single largest hazard in a multi-tracker workspace is having Linear, beads, and the OpenSpec tasks.md all compete to own the work-item ledger. This hub resolves that by ownership-by-layer, not by mirroring one layer into another. Linear owns the business "what" and coarse parent-issue status, pushed up one-way (local authoritative, Linear is a coarse projection). OpenSpec plus the superpowers-bridge own the spec-first change lifecycle, the human-interpretable requirements document, and the within-change task decomposition in tasks.md. beads owns the local dependency graph and is invoked for finer-grained tracking only when a complex task needs it; it is not the default decomposition owner. The mode-conditioned task ledger (which layer is authoritative depends on execution mode) is the router's concern; see the agentic-planning-development-workflow skill for that selection, and openspec-linear-sync for the Linear binding.
Read the workspace safety gate before proposing any Linear mutation.
| File | Description |
|---|---|
| references/linear-overview.md | The Initiative > Project > Milestone > Issue ontology, Cycles as a scheduling overlay, and the SYNC/NOSYNC issue-body section markers |
| references/linear-workspace-safety-gate.md | The hardest constraint: never mutate Linear until the workspace is confirmed via linear auth whoami; the five-tier credential precedence and why LINEAR_WORKSPACE is the wrong lever |
| references/linear-conventions.md | Issue body = TL;DR + Deliverables + Acceptance Criteria only; status in fields/comments; one-way status rollup; sizing; triage versus backlog versus deferral |
| File | Description |
|---|---|
| references/github-overview.md | The PR, buildbot, and Mergify surface; the monorepo PR (including docs/handbook) as one realization of the archived-OpenSpec-change terminal artifact |
| File | Description |
|---|---|
| references/beads-overview.md | beads as the optional local fine-grained drill-down sublayer; load-bearing in Manual mode; the beads-epic↔Linear-parent mapping and the branch-name-as-binding convention; routes to issues-beads |
| File | Description |
|---|---|
| references/method-overview.md | Synthesized Linear Method + CCPM principles: the ontology, Cycles-as-overlay, sizing and estimation, triage/backlog/deferral, SYNC/NOSYNC markers, and projects linking to (not duplicating) the specs that define correctness |
This hub composes existing surfaces and never re-implements them. For raw Linear command verbs invoke the bundled linear-cli skill. For the local issue graph and the bd CLI consult issues-beads. For binding a Linear story to an OpenSpec change and mirroring lifecycle phase to Linear state, use openspec-linear-sync. For selecting an execution mode and driving the board between states, use the agentic-planning-development-workflow router.
