format: apply repo prettier (3.8.1) to the folded skills tree
963 markdown files reformatted with the repository's pinned prettier so pnpm format:check covers the folded tree like every other repo file. The formatter's embedded-language pass also normalized code fences (TS semicolons, closed HTML tags in examples, lowercased CSS hex colors, one renumbered list that skipped an index). Alphanumeric token deltas vs the fold commit were audited file-by-file; all are formatter-equivalent markup normalizations plus the four sanitized skills.
This commit is contained in:
fargo
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: kickstart
|
||||
description: "Launch an orchestrator session for a milestone, issue, or task. Use when starting autonomous work on a milestone, orchestrating issue completion, or resuming from a handoff. Triggers on: kickstart, orchestrate, start milestone, resume orchestrator."
|
||||
description: 'Launch an orchestrator session for a milestone, issue, or task. Use when starting autonomous work on a milestone, orchestrating issue completion, or resuming from a handoff. Triggers on: kickstart, orchestrate, start milestone, resume orchestrator.'
|
||||
---
|
||||
|
||||
# Kickstart Orchestrator
|
||||
@@ -8,6 +8,7 @@ description: "Launch an orchestrator session for a milestone, issue, or task. Us
|
||||
Launch an orchestrator session with a single command. Replaces the manual boilerplate of specifying mission, quality gates, branch strategy, and tracking protocol.
|
||||
|
||||
**Usage:**
|
||||
|
||||
```
|
||||
/kickstart — List open milestones, ask user to pick
|
||||
/kickstart 0.0.9 — Orchestrate a milestone (by version)
|
||||
@@ -25,13 +26,13 @@ Launch an orchestrator session with a single command. Replaces the manual boiler
|
||||
|
||||
Parse the argument (if any) provided after `/kickstart`:
|
||||
|
||||
| Pattern | Type | Example |
|
||||
|---------|------|---------|
|
||||
| No argument | **interactive** | `/kickstart` |
|
||||
| Starts with `#` | **issue** | `/kickstart #42` |
|
||||
| `resume` (literal) | **resume** | `/kickstart resume` |
|
||||
| Contains `-` with uppercase + digits at end | **task ID** | `/kickstart MS-SEC-001` |
|
||||
| Anything else | **milestone** | `/kickstart 0.0.9` or `/kickstart M10-Telemetry` |
|
||||
| Pattern | Type | Example |
|
||||
| ------------------------------------------- | --------------- | ------------------------------------------------ |
|
||||
| No argument | **interactive** | `/kickstart` |
|
||||
| Starts with `#` | **issue** | `/kickstart #42` |
|
||||
| `resume` (literal) | **resume** | `/kickstart resume` |
|
||||
| Contains `-` with uppercase + digits at end | **task ID** | `/kickstart MS-SEC-001` |
|
||||
| Anything else | **milestone** | `/kickstart 0.0.9` or `/kickstart M10-Telemetry` |
|
||||
|
||||
### 1b. If no argument (interactive mode)
|
||||
|
||||
@@ -42,6 +43,7 @@ List open milestones and ask the user to choose:
|
||||
```
|
||||
|
||||
Present the results and ask:
|
||||
|
||||
```
|
||||
Which target do you want to orchestrate?
|
||||
A. [milestone 1]
|
||||
@@ -70,6 +72,7 @@ git branch -r | grep -E 'origin/(develop|main)' | head -1
|
||||
```
|
||||
|
||||
Read the project's `AGENTS.md` first (and `SOUL.md` if present). If only `CLAUDE.md` exists, use it as compatibility fallback. Scan for:
|
||||
|
||||
- Quality gate commands (look for `pnpm`, `npm`, `pytest`, `lint`, `typecheck`, `test`)
|
||||
- Branch conventions
|
||||
- Task prefix conventions
|
||||
@@ -132,6 +135,7 @@ Read the issue description, labels, and any linked milestone.
|
||||
### For resume target
|
||||
|
||||
Read `docs/tasks.md` and determine:
|
||||
|
||||
- How many tasks are `done` vs `not-started` vs `in-progress` vs `failed`
|
||||
- What the next unblocked task is
|
||||
- Whether any tasks are stuck (in-progress with no agent)
|
||||
@@ -149,11 +153,13 @@ Read ~/.config/mosaic/guides/orchestrator.md
|
||||
```
|
||||
|
||||
Also load skills relevant to the project's tech stack from project docs (`AGENTS.md`/`SOUL.md`) plus `~/.config/mosaic/STANDARDS.md`. For example:
|
||||
|
||||
- NestJS project → load `nestjs-best-practices`
|
||||
- Next.js project → load `next-best-practices`, `vercel-react-best-practices`
|
||||
- Python project → load `fastapi`, `python-performance-optimization`
|
||||
|
||||
Always load these orchestrator-relevant skills:
|
||||
|
||||
- `verification-before-completion` — evidence-based completion claims
|
||||
- `dispatching-parallel-agents` — parallel worker patterns
|
||||
|
||||
@@ -183,6 +189,7 @@ Then populate `docs/tasks.md` with tasks derived from the issues:
|
||||
- Create feature branches: `feature/<milestone-slug>` as the integration branch
|
||||
|
||||
Commit the bootstrap:
|
||||
|
||||
```bash
|
||||
git add docs/tasks.md docs/orchestrator-learnings.json
|
||||
git commit -m "chore: Bootstrap orchestrator for <target>"
|
||||
@@ -192,6 +199,7 @@ git push
|
||||
### 4b. Resume (existing tasks.md)
|
||||
|
||||
Read `docs/tasks.md` and validate:
|
||||
|
||||
- Schema matches expected format (id, status, description, issue, branch, etc.)
|
||||
- No tasks stuck in `in-progress` without an active agent
|
||||
- Dependencies are consistent (no circular deps, no done tasks blocking not-started)
|
||||
@@ -199,6 +207,7 @@ Read `docs/tasks.md` and validate:
|
||||
Mark any orphaned `in-progress` tasks as `not-started` (previous agent likely lost context).
|
||||
|
||||
Report to user:
|
||||
|
||||
```
|
||||
=== Resume Status ===
|
||||
Total tasks: 15
|
||||
@@ -262,12 +271,16 @@ When spawning a worker, provide this structure:
|
||||
**Base:** {develop|main}
|
||||
|
||||
### Requirements
|
||||
|
||||
{Issue description and acceptance criteria}
|
||||
|
||||
### Quality Gates (MANDATORY — zero tolerance)
|
||||
|
||||
Run ALL of these before reporting success. Fix every failure.
|
||||
```
|
||||
|
||||
{quality gate commands from project}
|
||||
|
||||
```
|
||||
**Linting is NON-NEGOTIABLE.** Run the project linter and fix ALL violations
|
||||
in every file you touched. Do NOT leave lint warnings, do NOT disable rules,
|
||||
@@ -314,17 +327,18 @@ Then STOP COMPLETELY. Do not continue working.
|
||||
|
||||
If project docs (`AGENTS.md`/`SOUL.md`/`CLAUDE.md`) don't specify quality gates, check for these patterns:
|
||||
|
||||
| File | Likely Quality Gates |
|
||||
|------|---------------------|
|
||||
| `package.json` with `scripts.lint` | `pnpm lint` or `npm run lint` |
|
||||
| `package.json` with `scripts.test` | `pnpm test` or `npm run test` |
|
||||
| `package.json` with `scripts.typecheck` | `pnpm typecheck` |
|
||||
| `tsconfig.json` | `pnpm tsc --noEmit` |
|
||||
| `pyproject.toml` | `pytest`, `ruff check`, `mypy` |
|
||||
| `.woodpecker.yml` | Parse pipeline steps for commands |
|
||||
| `Makefile` | `make lint`, `make test` |
|
||||
| File | Likely Quality Gates |
|
||||
| --------------------------------------- | --------------------------------- |
|
||||
| `package.json` with `scripts.lint` | `pnpm lint` or `npm run lint` |
|
||||
| `package.json` with `scripts.test` | `pnpm test` or `npm run test` |
|
||||
| `package.json` with `scripts.typecheck` | `pnpm typecheck` |
|
||||
| `tsconfig.json` | `pnpm tsc --noEmit` |
|
||||
| `pyproject.toml` | `pytest`, `ruff check`, `mypy` |
|
||||
| `.woodpecker.yml` | Parse pipeline steps for commands |
|
||||
| `Makefile` | `make lint`, `make test` |
|
||||
|
||||
If no quality gates can be detected, ask the user:
|
||||
|
||||
```
|
||||
I couldn't detect quality gate commands for this project.
|
||||
What commands should workers run to verify their changes?
|
||||
|
||||
Reference in New Issue
Block a user