backup skills
This commit is contained in:
@@ -0,0 +1,106 @@
|
||||
---
|
||||
name: project-skills-setup
|
||||
description: "Configure a repository for Linear-backed engineering skills."
|
||||
disable-model-invocation: true
|
||||
---
|
||||
|
||||
# Project Skills Setup
|
||||
|
||||
Configure the current repository once. Use Linear as the issue tracker, install the repository-local agent pointers, and create the Linear labels Wayfinder requires.
|
||||
|
||||
## 1. Reach Linear
|
||||
|
||||
Call the connected Linear MCP server's workspace operation.
|
||||
|
||||
If Linear MCP is unavailable:
|
||||
|
||||
1. Inspect `.omp/mcp.json` if it exists.
|
||||
2. Draft a merge that preserves every existing server and adds only:
|
||||
|
||||
```json
|
||||
"linear": {
|
||||
"type": "http",
|
||||
"url": "https://mcp.linear.app/mcp"
|
||||
}
|
||||
```
|
||||
|
||||
3. Show the complete resulting JSON and obtain approval before writing it.
|
||||
4. Validate the JSON, then tell the user to run `/mcp reload` and `/mcp reauth linear`.
|
||||
5. Stop. Resume this skill after the workspace operation succeeds.
|
||||
|
||||
OAuth credentials belong to the active OMP profile, never the repository. This step is complete when the authenticated workspace can be read.
|
||||
|
||||
## 2. Map the repository to Linear
|
||||
|
||||
Inspect:
|
||||
|
||||
- the repository directory name and VCS remote name;
|
||||
- root `CLAUDE.md` and `AGENTS.md`, including any existing `## Agent skills` section;
|
||||
- `docs/agents/`, `CONTEXT.md`, `CONTEXT-MAP.md`, `docs/adr/`, and context-scoped ADR directories;
|
||||
- genuine monorepo signals: `pnpm-workspace.yaml`, a root `package.json` `workspaces` field, or populated `packages/*/src` directories;
|
||||
- the authenticated Linear workspace, teams, projects, team workflow states, current user, and issue labels.
|
||||
|
||||
Resolve facts through the repository and Linear MCP rather than asking the user.
|
||||
|
||||
Recommend the project whose name or slug matches the repository name case-insensitively. Derive its owning team. With no project match, recommend an exact team match without creating a project. Ask one mapping question only when no unique match exists. A project is optional; a team is required.
|
||||
|
||||
Use the workflow-state names returned by Linear for the `unstarted`, `completed`, and `canceled` types. This step is complete when workspace, team, optional project, and those three state names are unambiguous.
|
||||
|
||||
## 3. Choose the domain layout
|
||||
|
||||
Use single-context unless the repository has the monorepo signals above. For a genuine monorepo, show the detected contexts and confirm multi-context. Do not create `CONTEXT.md`, `CONTEXT-MAP.md`, or ADRs; domain modeling creates them when the first term or durable decision exists.
|
||||
|
||||
This step is complete when the layout and every context path are known.
|
||||
|
||||
## 4. Draft the setup
|
||||
|
||||
Choose the instruction file in this order:
|
||||
|
||||
1. `CLAUDE.md` when it exists.
|
||||
2. Otherwise `AGENTS.md` when it exists.
|
||||
3. Ask which one to create only when neither exists.
|
||||
|
||||
Update an existing `## Agent skills` section in place. Otherwise append one containing only:
|
||||
|
||||
```markdown
|
||||
## Agent skills
|
||||
|
||||
### Issue tracker
|
||||
|
||||
Issues and Wayfinder maps are tracked in Linear under the `<team>` team<project-clause>. See `docs/agents/issue-tracker.md`.
|
||||
|
||||
### Domain docs
|
||||
|
||||
This repository uses the `<layout>` domain-doc layout. See `docs/agents/domain.md`.
|
||||
```
|
||||
|
||||
Read `issue-tracker.md` and `domain.md` from this skill directory. Substitute every placeholder and remove every inapplicable optional clause. Draft:
|
||||
|
||||
- the complete instruction-file edit;
|
||||
- `.omp/mcp.json` only when the Linear endpoint is not already discoverable;
|
||||
- `docs/agents/issue-tracker.md`;
|
||||
- `docs/agents/domain.md`;
|
||||
- these missing team-scoped labels: `wayfinder:map`, `wayfinder:research`, `wayfinder:prototype`, `wayfinder:grilling`, `wayfinder:task`.
|
||||
|
||||
Show the complete file contents and label changes together. Obtain one approval before applying the repository and Linear changes. This step is complete only with explicit approval of that exact draft.
|
||||
|
||||
## 5. Apply
|
||||
|
||||
Apply the approved draft exactly:
|
||||
|
||||
- preserve unrelated instruction and MCP configuration;
|
||||
- create or update the two `docs/agents/` files;
|
||||
- create only missing Wayfinder labels in the selected Linear team;
|
||||
- keep OAuth material out of repository files.
|
||||
|
||||
## 6. Verify
|
||||
|
||||
Verify all of the following before reporting completion:
|
||||
|
||||
- `.omp/mcp.json`, when written, parses as JSON and points to `https://mcp.linear.app/mcp`;
|
||||
- the chosen instruction file points to both existing `docs/agents/` files;
|
||||
- the tracker document names the resolved workspace, team, optional project, and actual workflow states;
|
||||
- Linear lists all five active Wayfinder labels in the selected team;
|
||||
- no domain glossary or ADR was created pre-emptively.
|
||||
|
||||
Report the files changed, Linear objects created, and the exact checks performed.
|
||||
Reference in New Issue
Block a user