120 lines
7.1 KiB
Markdown
120 lines
7.1 KiB
Markdown
---
|
|
name: configure-skills
|
|
description: "Configure this repo for the design and develop skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other design and develop skills."
|
|
disable-model-invocation: true
|
|
---
|
|
|
|
# Configure Skills
|
|
|
|
Scaffold the per-repo configuration that the design and develop skills assume:
|
|
|
|
- **Issue tracker**: where issues live (Gitea by default; local markdown is also supported out of the box)
|
|
- **Triage labels**: the strings used for the five canonical triage roles
|
|
- **Domain docs**: where `CONTEXT.md` and ADRs live, and the consumer rules for reading them
|
|
- **Sub-agents**: a basic instruction to delegate through Paseo's CLI
|
|
|
|
This is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.
|
|
|
|
## Process
|
|
|
|
### 1. Explore
|
|
|
|
Look at the current repo to understand its starting state. Read whatever exists; don't assume:
|
|
|
|
- `git remote -v` and `.git/config`: which remote should `tea` use?
|
|
- `tea logins list --output json`: is the matching Gitea instance configured? Never print or copy tokens from tea's config.
|
|
- `AGENTS.md` and `CLAUDE.md` at the repo root: does either exist? Is there already an `## Agent skills` section in either?
|
|
- `CONTEXT.md` and `CONTEXT-MAP.md` at the repo root
|
|
- `docs/adr/` and any `src/*/docs/adr/` directories
|
|
- `docs/agents/`: does this skill's prior output already exist?
|
|
- `.scratch/`: a sign that a local-markdown issue tracker convention is already in use
|
|
- Is the `triage` skill installed? (a `triage` skill folder alongside this one, or `triage` in your available skills.) This decides whether Section B runs at all.
|
|
- Monorepo signals: a `pnpm-workspace.yaml`, a `workspaces` field in `package.json`, or a populated `packages/*` with its own `src/`. These are present only in a genuinely large multi-package repo; their absence means single-context, which is almost every repo.
|
|
|
|
### 2. Present findings and ask
|
|
|
|
Summarise what's present and what's missing. Then take the sections in order. One section, one answer, then the next.
|
|
|
|
Lead each section with the recommended answer so the user can accept it in a word. Give a one-line explainer only when the choice genuinely branches; skip the section entirely when exploration already settled it (Section B when `triage` isn't installed, Section C when there's no monorepo).
|
|
|
|
**Section A: Issue tracker.**
|
|
|
|
> Explainer: The "issue tracker" is where issues live for this repo. Skills like `to-tickets`, `triage`, and `to-spec` read from and write to it. They need to know whether to call `tea issues create` or write a markdown file under `.scratch/`. Pick the place you actually track work for this repo.
|
|
|
|
Default to **Gitea** whenever the repo has a Gitea remote. Confirm which remote/login to use if there is more than one. If the matching instance is not configured in `tea`, stop and ask the user to run `tea login add`; do not request or handle their access token.
|
|
|
|
Offer **local markdown** only when there is no Gitea remote or the user explicitly wants repository-local tickets:
|
|
|
|
- **Gitea**: issues live in the repo's Gitea Issues and all remote operations use the `tea` CLI
|
|
- **Local markdown**: issues live as files under `.scratch/<feature>/` in this repo (good for repos that are not published to Gitea)
|
|
|
|
Record the choice in `docs/agents/issue-tracker.md`. The Gitea template carries a "PRs as a request surface" flag, defaulted **off**. Leave it off and don't raise it: a user who wants external PRs in the triage queue can flip the flag in the file later.
|
|
|
|
**Section B: Triage label vocabulary.** Skip this section entirely if the `triage` skill isn't installed (exploration told you), since an uninstalled skill needs no labels.
|
|
|
|
If it is installed, ask exactly one question:
|
|
|
|
> Do you want to keep the default triage labels? (recommended: **yes**)
|
|
|
|
The defaults are the five canonical roles, each label string equal to its name: `needs-triage`, `needs-info`, `ready-for-agent`, `ready-for-human`, `wontfix`. On **yes**, write them as-is. Only if the user says no, usually because their tracker already uses other names (e.g. `bug:triage` for `needs-triage`), collect the overrides so `triage` applies existing labels instead of creating duplicates.
|
|
|
|
**Section C: Domain docs.** Default to **single-context** (one `CONTEXT.md` + `docs/adr/` at the repo root). This fits almost every repo; write it without asking.
|
|
|
|
Offer **multi-context** (a root `CONTEXT-MAP.md` pointing to per-context `CONTEXT.md` files) only when exploration found monorepo signals. Then confirm which layout they want.
|
|
|
|
### 3. Confirm and edit
|
|
|
|
Show the user a draft of:
|
|
|
|
- The `## Agent skills` block to add to whichever of `CLAUDE.md` / `AGENTS.md` is being edited (see step 4 for selection rules), including the Paseo sub-agent instructions
|
|
- The contents of `docs/agents/issue-tracker.md`, `docs/agents/domain.md`, and `docs/agents/triage-labels.md` (the last only when `triage` is installed)
|
|
|
|
Let them edit before writing.
|
|
|
|
### 4. Write
|
|
|
|
**Pick the file to edit:**
|
|
|
|
- If `CLAUDE.md` exists, edit it.
|
|
- Else if `AGENTS.md` exists, edit it.
|
|
- If neither exists, ask the user which one to create; don't pick for them.
|
|
|
|
Never create `AGENTS.md` when `CLAUDE.md` already exists (or vice versa); always edit the one that's already there.
|
|
|
|
If an `## Agent skills` block already exists in the chosen file, update its contents in-place rather than appending a duplicate. Don't overwrite user edits to the surrounding sections.
|
|
|
|
The block:
|
|
|
|
```markdown
|
|
## Agent skills
|
|
|
|
### Issue tracker
|
|
|
|
[one-line summary of where issues are tracked]. See `docs/agents/issue-tracker.md`.
|
|
|
|
### Triage labels
|
|
|
|
[one-line summary of the label vocabulary]. See `docs/agents/triage-labels.md`.
|
|
|
|
### Domain docs
|
|
|
|
[one-line summary of layout: "single-context" or "multi-context"]. See `docs/agents/domain.md`.
|
|
|
|
### Sub-agents
|
|
|
|
Delegate sub-agent work through the Paseo CLI. Start work asynchronously in the current workspace with `paseo run --background --title "<task>" "<self-contained prompt>"`; use `--new-workspace worktree` plus the appropriate worktree mode when the task needs isolated edits. Use `paseo send <agent-id> "<follow-up>"` for follow-ups. Let Paseo's completion notification report the result instead of polling. Run `paseo --help`, `paseo run --help`, or `paseo provider ls` when launch details or provider availability are unclear.
|
|
```
|
|
|
|
Include the `### Triage labels` sub-block, and write `docs/agents/triage-labels.md`, only when `triage` is installed and Section B ran. When it isn't, both are omitted.
|
|
|
|
Then write the docs files using the seed templates in this skill folder as a starting point:
|
|
|
|
- [issue-tracker-gitea.md](./issue-tracker-gitea.md): Gitea issue tracker using `tea`
|
|
- [issue-tracker-local.md](./issue-tracker-local.md): local-markdown issue tracker
|
|
- [triage-labels.md](./triage-labels.md): label mapping (only if `triage` is installed)
|
|
- [domain.md](./domain.md): domain doc consumer rules + layout
|
|
|
|
### 5. Done
|
|
|
|
Tell the user the setup is complete and which engineering skills will now read from these files. Mention they can edit `docs/agents/*.md` directly later; re-running this skill is only necessary if they want to switch issue trackers or restart from scratch.
|