@installagent/sdk 0.1.0 → 0.3.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/agent-mirror.d.ts +69 -0
- package/dist/agent-mirror.js +275 -0
- package/dist/agent-templates.d.ts +36 -2
- package/dist/agent-templates.js +173 -3
- package/dist/claude-hours.d.ts +118 -0
- package/dist/claude-hours.js +523 -0
- package/dist/client-drive.d.ts +3 -0
- package/dist/client-drive.js +2 -2
- package/dist/client-linear-create.d.ts +26 -0
- package/dist/client-linear-create.js +46 -0
- package/dist/client-linear.d.ts +28 -9
- package/dist/client-linear.js +36 -14
- package/dist/docs-search.d.ts +19 -6
- package/dist/docs-search.js +32 -11
- package/dist/doctor.d.ts +9 -0
- package/dist/doctor.js +126 -23
- package/dist/env-fill.d.ts +13 -0
- package/dist/env-fill.js +55 -13
- package/dist/env-push.d.ts +3 -0
- package/dist/env-push.js +11 -6
- package/dist/env-registry.d.ts +29 -0
- package/dist/env-registry.js +123 -9
- package/dist/exec.js +15 -2
- package/dist/git.d.ts +31 -0
- package/dist/git.js +59 -0
- package/dist/google-service-account.d.ts +20 -0
- package/dist/google-service-account.js +49 -0
- package/dist/hours-estimate.d.ts +43 -0
- package/dist/hours-estimate.js +159 -0
- package/dist/hours-export-schedule.d.ts +35 -0
- package/dist/hours-export-schedule.js +188 -0
- package/dist/hours-ledger.d.ts +129 -0
- package/dist/hours-ledger.js +882 -0
- package/dist/index.d.ts +25 -6
- package/dist/index.js +25 -6
- package/dist/linear-project.d.ts +2 -2
- package/dist/linear-project.js +2 -2
- package/dist/log.d.ts +28 -0
- package/dist/log.js +73 -0
- package/dist/n8n-executions.d.ts +85 -0
- package/dist/n8n-executions.js +259 -0
- package/dist/op-cli.d.ts +29 -0
- package/dist/op-cli.js +52 -0
- package/dist/platform.d.ts +35 -0
- package/dist/platform.js +39 -0
- package/dist/portal-admin.d.ts +108 -0
- package/dist/portal-admin.js +94 -1
- package/dist/standup.d.ts +88 -0
- package/dist/standup.js +235 -0
- package/dist/sync-repos.d.ts +54 -0
- package/dist/sync-repos.js +89 -0
- package/dist/template-sync.d.ts +11 -0
- package/dist/template-sync.js +16 -0
- package/dist/triage-backfill.d.ts +37 -0
- package/dist/triage-backfill.js +211 -0
- package/dist/triage-enable.d.ts +90 -0
- package/dist/triage-enable.js +428 -0
- package/dist/triage-gates.d.ts +252 -0
- package/dist/triage-gates.js +951 -0
- package/dist/wizard.d.ts +15 -0
- package/dist/wizard.js +35 -56
- package/dist/workspace-docs.d.ts +44 -0
- package/dist/workspace-docs.js +73 -0
- package/dist/workspace-push.d.ts +39 -0
- package/dist/workspace-push.js +78 -0
- package/dist/workspace-status.d.ts +37 -0
- package/dist/workspace-status.js +114 -0
- package/package.json +2 -2
- package/templates/env.example +37 -23
- package/templates/workspace-root/.claude/settings.json +12 -1
- package/templates/workspace-root/AGENT.md +7 -5
- package/templates/workspace-root/ONBOARDING.md +65 -8
- package/templates/workspace-root/skills/.github/workflows/pr-to-slack.yml +127 -0
- package/templates/workspace-root/skills/CLAUDE.md +29 -6
- package/templates/workspace-root/skills/README.md +171 -0
- package/templates/workspace-root/skills/ad-machine/SKILL.md +140 -0
- package/templates/workspace-root/skills/backtest-acceptance-gates/SKILL.md +293 -0
- package/templates/workspace-root/skills/backtest-acceptance-gates/backtest-acceptance-gates-guide.pdf +0 -0
- package/templates/workspace-root/skills/backtest-acceptance-gates/references/evidence-record-template.md +128 -0
- package/templates/workspace-root/skills/backtest-acceptance-gates/references/harness-checklist.md +90 -0
- package/templates/workspace-root/skills/client-deliverables/SKILL.md +1 -1
- package/templates/workspace-root/skills/client-deliverables/references/package-layout.md +3 -2
- package/templates/workspace-root/skills/client-latest/SKILL.md +343 -0
- package/templates/workspace-root/skills/client-latest/catchup.command.md +18 -0
- package/templates/workspace-root/skills/cloud-devops/SKILL.md +235 -0
- package/templates/workspace-root/skills/email-triage-rollout/SKILL.md +258 -0
- package/templates/workspace-root/skills/engagement-spec/SKILL.md +51 -18
- package/templates/workspace-root/skills/engagement-spec/references/spec-templates.md +10 -4
- package/templates/workspace-root/skills/gcloud-cli-setup/SKILL.md +100 -0
- package/templates/workspace-root/skills/github-profile/SKILL.md +106 -0
- package/templates/workspace-root/skills/google-chat-app-setup/SKILL.md +136 -0
- package/templates/workspace-root/skills/google-chat-app-setup/google-chat-app-setup-guide.pdf +0 -0
- package/templates/workspace-root/skills/house-voice/SKILL.md +80 -4
- package/templates/workspace-root/skills/ia-cli/SKILL.md +49 -7
- package/templates/workspace-root/skills/init_repo/SKILL.md +188 -0
- package/templates/workspace-root/skills/installagent-brand-kit/SKILL.md +59 -10
- package/templates/workspace-root/skills/installagent-brand-kit/assets/installagent-deck-template.pptx +0 -0
- package/templates/workspace-root/skills/installagent-brand-kit/references/deck-guide.md +181 -0
- package/templates/workspace-root/skills/installagent-brand-kit/scripts/deck.py +652 -0
- package/templates/workspace-root/skills/installagent-brand-kit/scripts/deck_lint.py +201 -0
- package/templates/workspace-root/skills/installagent-brand-kit/scripts/logo_raster.py +102 -0
- package/templates/workspace-root/skills/installagent-brand-kit/scripts/make_deck_template.py +290 -0
- package/templates/workspace-root/skills/salesforce-api-snapshot/SKILL.md +379 -0
- package/templates/workspace-root/skills/salesforce-api-snapshot/references/schema-discovery-soql.md +153 -0
- package/templates/workspace-root/skills/salesforce-api-snapshot/references/snapshot-storage.md +122 -0
- package/templates/workspace-root/skills/salesforce-api-snapshot/salesforce-api-snapshot-guide.pdf +0 -0
- package/templates/workspace-root/skills/slack-voice/SKILL.md +158 -0
- package/templates/workspace-root/skills/sso-gated-client-app/SKILL.md +337 -0
- package/templates/workspace-root/skills/sso-gated-client-app/sso-gated-client-app-guide.pdf +0 -0
- package/templates/workspace-root/skills/tech-call-prep/SKILL.md +146 -47
- package/templates/workspace-root/skills/vendor-feed-ingestion/SKILL.md +323 -0
- package/templates/workspace-root/skills/vendor-feed-ingestion/references/delivery-contract-template.md +110 -0
- package/templates/workspace-root/skills/vendor-feed-ingestion/references/feed-guards.md +134 -0
- package/templates/workspace-root/skills/vendor-feed-ingestion/vendor-feed-ingestion-guide.pdf +0 -0
|
@@ -0,0 +1,343 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: client-latest
|
|
3
|
+
description: >-
|
|
4
|
+
Catch a technician (or an agent) up on one client engagement so they can
|
|
5
|
+
resume the build — a two-part terminal brief: where it stands right now
|
|
6
|
+
(bulleted, by system), then one ranked table of what's wrong and what to
|
|
7
|
+
do about it. Reads the build repo (CLIENT.md, docs/00-delivery-log.md,
|
|
8
|
+
evidence/, onboarding.html, AGENT.md gotchas), the local git state
|
|
9
|
+
(uncommitted, unpushed, open PRs, stray worktrees), the read-only
|
|
10
|
+
`ia client` / `ia client-linear` commands, the calendar (the one date a
|
|
11
|
+
repo cannot be trusted for), the client's Slack channel, and n8n run
|
|
12
|
+
health via `ia agent executions`. Use this WHENEVER someone says "what's
|
|
13
|
+
the latest on [client]", "catch me up on [client]", "where did we leave
|
|
14
|
+
off", "resume the [client] build", "status of [client]", "what's blocked
|
|
15
|
+
on [client]", "did anything drift", "am I missing anything before I
|
|
16
|
+
start", or opens a `clients/client-[slug]/` repo cold. Reach for it even
|
|
17
|
+
if the user never says "skill". The brief itself is a pure read; if the
|
|
18
|
+
ranked table has anything in it, it then asks how you want to move
|
|
19
|
+
forward (fix the drift, or start one of the ranked items) and acts on the
|
|
20
|
+
answer — in the working tree only, never a commit, never a push. Not call
|
|
21
|
+
prep: an upcoming client call goes to `tech-call-prep` instead.
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
# client-latest — resume-the-build brief for one client
|
|
25
|
+
|
|
26
|
+
One engagement is described in four places that nothing keeps in step:
|
|
27
|
+
Linear, `docs/`, `onboarding.html`, and the live systems. This skill reads
|
|
28
|
+
all of them in one pass and prints what is true, then what disagrees.
|
|
29
|
+
|
|
30
|
+
**The brief is a read.** Print it in the terminal. Write no status file —
|
|
31
|
+
one would itself go stale and become another drift source, which is the
|
|
32
|
+
exact failure `CADENCE.md` exists to stop.
|
|
33
|
+
|
|
34
|
+
**If the ranked table (see Output below) has anything in it**, ask how the
|
|
35
|
+
reader wants to move forward, and act on the answer. If it's empty, say so
|
|
36
|
+
and stop — don't ask a question with no real options. The gathering steps
|
|
37
|
+
never write. Only an explicit choice in the CTA does, and even then the
|
|
38
|
+
work **stops in the working tree**: no commit, no push, no PR.
|
|
39
|
+
|
|
40
|
+
## Inputs
|
|
41
|
+
|
|
42
|
+
- **Client slug** — from the argument (`jared-tomseth`), a repo path
|
|
43
|
+
(`clients/client-jared-tomseth/`), or the current directory when you are
|
|
44
|
+
already inside a client repo. A company name that is not a slug
|
|
45
|
+
(`Medearis`) resolves through `team-clients/clients/*/PROFILE.md`; if two
|
|
46
|
+
match, ask — never guess which client you are reporting on.
|
|
47
|
+
- **Nothing else.** No pasted context needed. If a source cannot be read,
|
|
48
|
+
the brief says so; it does not infer.
|
|
49
|
+
|
|
50
|
+
## The window
|
|
51
|
+
|
|
52
|
+
Two anchors, and you take the **wider** of them:
|
|
53
|
+
|
|
54
|
+
1. the date of the newest entry in `docs/00-delivery-log.md`;
|
|
55
|
+
2. today minus 7 days.
|
|
56
|
+
|
|
57
|
+
So a busy client always gets at least 7 days, and a quiet client gets
|
|
58
|
+
everything back to the last thing anyone wrote down. State the window and
|
|
59
|
+
both anchors in the header — a log entry from three weeks ago is itself a
|
|
60
|
+
finding.
|
|
61
|
+
|
|
62
|
+
## The read order — one pass, no subagents
|
|
63
|
+
|
|
64
|
+
Run it in this order. Each step is cheap and narrows the next.
|
|
65
|
+
|
|
66
|
+
### 1. The manifest
|
|
67
|
+
|
|
68
|
+
`cat clients/client-<slug>/CLIENT.md`. It maps every external system.
|
|
69
|
+
Note any key that is still a placeholder (`<...>`, or a literal
|
|
70
|
+
`client-<slug>`) — an unfilled key is a drift finding, not a detail.
|
|
71
|
+
|
|
72
|
+
### 2. The repo, in the window
|
|
73
|
+
|
|
74
|
+
- `docs/00-delivery-log.md` — entries in the window. Newest first. This is
|
|
75
|
+
the "what shipped, does it work" record.
|
|
76
|
+
- `evidence/` — files dated in the window. An accuracy or go-live claim
|
|
77
|
+
with no evidence file is a risk, not a fact.
|
|
78
|
+
- `onboarding.html` — find the status snapshot and its **`AS OF` date**.
|
|
79
|
+
Compare that date to the newest log entry.
|
|
80
|
+
- `AGENT.md` § *Client-specific gotchas* — the traps for this repo. Carry
|
|
81
|
+
any that still apply into the risks/next table.
|
|
82
|
+
- `docs/` index — a high-numbered handoff or decision-log doc
|
|
83
|
+
(`NN-...-handoff.md`) is usually the freshest single page. Read it.
|
|
84
|
+
|
|
85
|
+
### 3. Git state — where work goes missing
|
|
86
|
+
|
|
87
|
+
```bash
|
|
88
|
+
cd clients/client-<slug>
|
|
89
|
+
git status --porcelain # uncommitted work
|
|
90
|
+
git log --oneline @{u}..HEAD # committed but never pushed
|
|
91
|
+
git log --oneline --since=<window-start>
|
|
92
|
+
gh pr list --state open # if the repo pushes to GitHub
|
|
93
|
+
git worktree list
|
|
94
|
+
```
|
|
95
|
+
|
|
96
|
+
Built-but-unlanded work is the most common real risk in this workspace —
|
|
97
|
+
it's the "Git vs reality" row in the drift table below, and it belongs
|
|
98
|
+
there even when the count is zero (say "clean" in the row rather than
|
|
99
|
+
omitting it). Also check `.claude/worktrees/` — a stale worktree holds a
|
|
100
|
+
full duplicate `docs/` tree, and reading the wrong copy produces a
|
|
101
|
+
confidently wrong brief.
|
|
102
|
+
|
|
103
|
+
**A PR that's green and ready to merge is not a passive fact — put it in
|
|
104
|
+
the ranked table as an action**, not just a count in the drift row. The
|
|
105
|
+
distinction: "3 unpushed commits" is drift (something disagrees with
|
|
106
|
+
reality); "PR #25 is green, waiting on a merge click" is a one-line fix,
|
|
107
|
+
so it belongs in NEXT-worthy rows even though nothing is technically
|
|
108
|
+
wrong yet.
|
|
109
|
+
|
|
110
|
+
Never commit, never push, never force-push to undo something you find.
|
|
111
|
+
|
|
112
|
+
### 4. The `ia` read-only commands
|
|
113
|
+
|
|
114
|
+
```bash
|
|
115
|
+
ia client <slug> # registry profile + recent calls + delivery log
|
|
116
|
+
ia client-linear <slug> # OPEN issues in the client's Linear project
|
|
117
|
+
```
|
|
118
|
+
|
|
119
|
+
`ia client-build` and `ia client-drive` are for when the local repo is thin
|
|
120
|
+
or a referenced doc is missing locally. Do not hand-roll GitHub, Airtable,
|
|
121
|
+
Linear, or Drive calls — see the `ia-cli` skill.
|
|
122
|
+
|
|
123
|
+
### 5. The calendar — the one date the repo cannot be trusted for
|
|
124
|
+
|
|
125
|
+
One query: `angello@installagent.com`'s calendar across the surrounding
|
|
126
|
+
week. Take the client's **next** and **last** meeting from it. Match the
|
|
127
|
+
client by attendee email domain (the registry `PROFILE.md` has the
|
|
128
|
+
addresses), never by the event title.
|
|
129
|
+
|
|
130
|
+
Then **date-check the repo against it.** Every date the docs state for a
|
|
131
|
+
call is a claim, and it goes stale in silence. One build repo carried "the
|
|
132
|
+
08-20 call" in 14 live places — tech spec, contract, handoff page, a
|
|
133
|
+
client-facing page, even a source comment — while the calendar said 08-21.
|
|
134
|
+
It survived nine days, a delivery-log entry, and a status refresh. Nothing
|
|
135
|
+
inside the repo can catch that. Only the calendar can.
|
|
136
|
+
|
|
137
|
+
- Put the next meeting, with its time zone, in the brief's first block.
|
|
138
|
+
- **Fathom cannot replace this.** It shows only calls that were held *and*
|
|
139
|
+
recorded, so it can never prove what is booked.
|
|
140
|
+
- An attendee who appears nowhere in the registry is a finding, not a
|
|
141
|
+
detail — that is a stakeholder someone is about to meet cold.
|
|
142
|
+
- **Never rewrite history to match.** A dated delivery-log entry records
|
|
143
|
+
what was believed then; correct it with a new entry, not an edit.
|
|
144
|
+
|
|
145
|
+
### 6. Slack — the client's own words
|
|
146
|
+
|
|
147
|
+
Read `slack_channel` from `CLIENT.md`. Read the channel back to the window
|
|
148
|
+
start. The convention is `#client-<slug>`, but real names vary (one has a
|
|
149
|
+
trailing hyphen; one client has both `#client-<slug>` and a `-team`
|
|
150
|
+
channel), so **use the key, do not build the name**. If the key says
|
|
151
|
+
`none`, print "no Slack channel" and move on. If the key is absent — or the channel it names
|
|
152
|
+
cannot be found — search once, then say in the brief which channel you
|
|
153
|
+
actually read. `ia client-intake` fills this key from the convention, so
|
|
154
|
+
a brand-new repo's value may still be a guess.
|
|
155
|
+
|
|
156
|
+
What matters here: a client ask that never reached Linear or the docs, an
|
|
157
|
+
unanswered question, and a promise we made.
|
|
158
|
+
|
|
159
|
+
**Credentials in the channel.** Clients paste passwords and keys into
|
|
160
|
+
Slack. If you see one, report *that it happened* and that it needs
|
|
161
|
+
rotating and deleting. Never echo the value into the brief, a file, a
|
|
162
|
+
commit message, or a Linear issue.
|
|
163
|
+
|
|
164
|
+
### 7. n8n run health
|
|
165
|
+
|
|
166
|
+
Workflow IDs are **not** in the repo's `workflows/*.json` — those exports
|
|
167
|
+
are sanitized, so the `id` field is stripped. They live in the docs:
|
|
168
|
+
|
|
169
|
+
```bash
|
|
170
|
+
grep -rIoh '`[A-Za-z0-9]\{16\}`' docs/ evidence/ AGENT.md | sort | uniq -c | sort -rn
|
|
171
|
+
ia agent executions <workflowId> -n 20
|
|
172
|
+
```
|
|
173
|
+
|
|
174
|
+
A 16-character backticked string is an n8n workflow id. The most-cited one
|
|
175
|
+
is usually the live workflow, but confirm it against the tech spec before
|
|
176
|
+
you report on it — never guess an id from the client name.
|
|
177
|
+
|
|
178
|
+
Report last run, last error, and silence (a workflow that should run daily
|
|
179
|
+
and has not run). Flag "built but never published" — an inactive or draft
|
|
180
|
+
workflow while the docs or Linear call it live.
|
|
181
|
+
|
|
182
|
+
Do **not** pass `--data`: run data holds full client payloads. Do not
|
|
183
|
+
manually execute a client workflow to "see if it works".
|
|
184
|
+
|
|
185
|
+
## The drift checks
|
|
186
|
+
|
|
187
|
+
Run every one. Report each as a pair of surfaces that disagree, with file
|
|
188
|
+
and line.
|
|
189
|
+
|
|
190
|
+
| Check | Drift looks like |
|
|
191
|
+
|---|---|
|
|
192
|
+
| Linear vs delivery log | Issue is Done, no log entry exists — or the log says shipped while the issue sits In Progress |
|
|
193
|
+
| `onboarding.html` vs delivery log | The `AS OF` snapshot date is older than the newest log entry |
|
|
194
|
+
| Log vs git | An entry claims a deploy or merge with no matching commit in the window |
|
|
195
|
+
| Git vs reality | Uncommitted files, unpushed commits, or an open PR — whether or not a log entry claims it shipped. State "clean" here explicitly when there's nothing, rather than omitting the row |
|
|
196
|
+
| `CLIENT.md` | A key still holds a placeholder, so every tool that resolves through it is guessing |
|
|
197
|
+
| n8n vs docs | Workflow inactive or draft while docs, Linear, or the client believe it is live |
|
|
198
|
+
| Evidence | A log entry links `evidence/<file>.md` that does not exist, or an evidence file no entry mentions |
|
|
199
|
+
| Worktrees | A `.claude/worktrees/` copy of `docs/` is newer than the tracked one |
|
|
200
|
+
|
|
201
|
+
## Output — state, then one ranked table
|
|
202
|
+
|
|
203
|
+
Print exactly this shape. Markdown, no preamble, no restating the inputs.
|
|
204
|
+
Tables over prose wherever there's more than one column of facts — a reader
|
|
205
|
+
should be able to scan the whole brief in the time it takes to read one
|
|
206
|
+
screen, not parse paragraphs. **This is a terminal brief, not the delivery
|
|
207
|
+
log** — one line per fact, cite the source instead of narrating how you
|
|
208
|
+
found it, and leave the "why" and the history in the repo files the source
|
|
209
|
+
column points at.
|
|
210
|
+
|
|
211
|
+
```
|
|
212
|
+
## <CLIENT NAME> (<slug>) — build repo clean? YES|NO
|
|
213
|
+
Window: <start> → today (log anchor <date> · 7-day anchor <date>)
|
|
214
|
+
|
|
215
|
+
### Where it stands
|
|
216
|
+
- **<system/component>:** <state, present tense, ≤12 words> (<source>)
|
|
217
|
+
- **<system/component>:** <state, present tense, ≤12 words> (<source>)
|
|
218
|
+
...max 6 bullets — one per production system, workflow, or track, not
|
|
219
|
+
per event. Merge same-system updates into the one bullet that matters now.
|
|
220
|
+
|
|
221
|
+
### Drift
|
|
222
|
+
| Surface A | Surface B | Disagreement | Location |
|
|
223
|
+
|---|---|---|---|
|
|
224
|
+
| <e.g. onboarding.html> | <e.g. delivery log> | <what they disagree on, ≤12 words> | <file:line> |
|
|
225
|
+
| Git vs reality | — | <clean, or n uncommitted / n unpushed / PR #n open+state> | <path> |
|
|
226
|
+
...max 5 rows, ranked by what's at stake. If more exist, add one line below
|
|
227
|
+
the table: "+n more drift rows not shown."
|
|
228
|
+
|
|
229
|
+
### Risks & next steps, worst first
|
|
230
|
+
| # | Risk / gap | Blocks | Fix | Source |
|
|
231
|
+
|---|---|---|---|---|
|
|
232
|
+
| 1 | <the problem, ≤12 words> | <what it blocks, or "—"> | <the concrete next step, ≤12 words> | <INS-xxx / file:line> |
|
|
233
|
+
| 2 | ... | | | |
|
|
234
|
+
...max 5 rows. If more exist, add one line below the table: "+n more rows
|
|
235
|
+
not shown" — the CTA's slot 3 is how the reader sees them.
|
|
236
|
+
|
|
237
|
+
### Could not read
|
|
238
|
+
- <source> — <why, ≤10 words>
|
|
239
|
+
```
|
|
240
|
+
|
|
241
|
+
One table, not two. A row doesn't have to be a live threat to belong here
|
|
242
|
+
— "PR #25 is green, needs a merge click" earns a row with `Blocks: —` and
|
|
243
|
+
`Fix: merge it`, same as a lost credential earns a row with `Blocks:
|
|
244
|
+
cutover`. Ranking still runs by what's actually at stake: a blocked
|
|
245
|
+
checkpoint outranks a one-click merge, which outranks a stale sentence in
|
|
246
|
+
a doc.
|
|
247
|
+
|
|
248
|
+
Rules for the output:
|
|
249
|
+
|
|
250
|
+
- **Rank by what's at stake**, not by how recent it is or whether it's
|
|
251
|
+
"technically" a risk. A lost credential that blocks a checkpoint beats a
|
|
252
|
+
green PR waiting on a click, which beats a stale sentence in a doc.
|
|
253
|
+
- **Every row carries a source.** `docs/00-delivery-log.md:41`, `INS-218`,
|
|
254
|
+
`#client-<slug> 08-19`. A row with no source does not go in.
|
|
255
|
+
- **No separate "unlanded" bucket.** Uncommitted files, unpushed commits,
|
|
256
|
+
and open PRs are the "Git vs reality" drift row (state "clean" rather
|
|
257
|
+
than omitting it); anything actionable in there (a mergeable PR) also
|
|
258
|
+
gets its own row in the risks/next table so it isn't just reported and
|
|
259
|
+
forgotten.
|
|
260
|
+
- **`Could not read` is required** whenever a source failed — an
|
|
261
|
+
unauthenticated MCP session, a missing token, no Linear project. A brief
|
|
262
|
+
that silently skips Slack reads as "Slack was quiet".
|
|
263
|
+
- **Never print a secret, key, password, or client PII**, and never a
|
|
264
|
+
client's dollar amount into anything shared. Point at the system that
|
|
265
|
+
holds the value.
|
|
266
|
+
- **Hard caps, not suggestions:** ≤6 bullets in "Where it stands", ≤5 rows
|
|
267
|
+
each in Drift and Risks/next, every cell one line. Ranking already decides
|
|
268
|
+
what survives — cut the lowest-stakes rows, not the formatting. If
|
|
269
|
+
something doesn't fit in one line, that's a sign it belongs in the repo
|
|
270
|
+
file the source column points at, not in the brief.
|
|
271
|
+
- One line of history per bullet/row max — a fact and its source, not the
|
|
272
|
+
story of how it was found. If the brief still runs past a screen with the
|
|
273
|
+
caps applied, cut adjectives and context clauses before cutting rows.
|
|
274
|
+
|
|
275
|
+
## The CTA — ask only if there's something to act on
|
|
276
|
+
|
|
277
|
+
After the brief, check the drift table and the risks/next table. **If both
|
|
278
|
+
are empty, say "nothing open — repo's clean" and stop. Don't ask a
|
|
279
|
+
question with no real options** — a reader who wants nothing further will
|
|
280
|
+
just stop reading or move on; forcing a "nothing, thanks" choice on them
|
|
281
|
+
every time is friction, not care.
|
|
282
|
+
|
|
283
|
+
If either table has rows, ask **one** question with up to three options,
|
|
284
|
+
in this order:
|
|
285
|
+
|
|
286
|
+
| Slot | Option | Build it from |
|
|
287
|
+
|---|---|---|
|
|
288
|
+
| 1 | **Fix the drift** — name the count and the items | the Drift table |
|
|
289
|
+
| 2 | **Start the top item** — name it | row 1 of the risks/next table |
|
|
290
|
+
| 3 | **Pick a different row** — name how many exist | the other rows |
|
|
291
|
+
|
|
292
|
+
Omit a slot if its source table is empty (e.g. no drift → only offer 2 and
|
|
293
|
+
3). Never pad the list back to three with a "do nothing" option — that's
|
|
294
|
+
what silence is for.
|
|
295
|
+
|
|
296
|
+
Rules:
|
|
297
|
+
|
|
298
|
+
- **Mark work a person must do** with `[HUMAN STEPS FIRST]` and say which
|
|
299
|
+
step is theirs. A lost credential, a Vercel redeploy, an `op` login, a
|
|
300
|
+
new OAuth credential in n8n — offering to "start" these without the
|
|
301
|
+
marker wastes the reader's time.
|
|
302
|
+
- **Slot 3 opens a second question** listing up to four rows. Say in it how
|
|
303
|
+
many rows exist and how many are not shown.
|
|
304
|
+
- **In an unattended run** (a `/loop`, a cron, a subagent), print the
|
|
305
|
+
available options as plain text and stop there. Never pick on the
|
|
306
|
+
reader's behalf.
|
|
307
|
+
|
|
308
|
+
### If they choose "fix the drift"
|
|
309
|
+
|
|
310
|
+
Fix **every mechanical drift row in one pass**, then show one combined diff
|
|
311
|
+
and stop. Mechanical means the fact is not in dispute: a stale date, a
|
|
312
|
+
status snapshot that contradicts the delivery log, a missing evidence
|
|
313
|
+
link, an unfilled `CLIENT.md` key whose real value is in the repo.
|
|
314
|
+
|
|
315
|
+
- **Repo files only.** A change to Linear, n8n, Airtable, Drive, or Slack
|
|
316
|
+
is a write to a **shared** surface, and discarding a diff cannot undo it.
|
|
317
|
+
List those instead, with the exact command or issue id, under
|
|
318
|
+
`YOUR CALL — SHARED SURFACES`. Then stop.
|
|
319
|
+
- **Never invent the fixed value.** If two surfaces disagree and the repo
|
|
320
|
+
cannot say which is right, that row is not mechanical. Leave it, and say
|
|
321
|
+
why in one line.
|
|
322
|
+
- **`CADENCE.md` still governs.** A drift fix that moves the shape of a
|
|
323
|
+
flow needs the diagram and the tech spec in the same change. If the fix
|
|
324
|
+
reaches that far, stop and say so — that is a slice, not a tidy-up.
|
|
325
|
+
- **Stop in the working tree.** Print `git status --porcelain` and hand the
|
|
326
|
+
commit to the reader. Never commit, never push, never force-push.
|
|
327
|
+
|
|
328
|
+
### If they choose a row from the risks/next table
|
|
329
|
+
|
|
330
|
+
Restate the item as a one-line contract before touching anything — the
|
|
331
|
+
trigger, the inputs, the outputs, the failure behavior. That is CADENCE
|
|
332
|
+
stage 1, and it is where the reader corrects you cheaply. Then work the
|
|
333
|
+
item, and stop in the working tree as above.
|
|
334
|
+
|
|
335
|
+
## What this skill is not
|
|
336
|
+
|
|
337
|
+
| If the task is… | Use |
|
|
338
|
+
|---|---|
|
|
339
|
+
| Prepping for an upcoming client call | `tech-call-prep` |
|
|
340
|
+
| Writing a call up into build docs | `engagement-spec` |
|
|
341
|
+
| Fixing the drift this brief found | `CADENCE.md` in that repo — the five stages, one commit per slice |
|
|
342
|
+
| Proving an accuracy number | `backtest-acceptance-gates` |
|
|
343
|
+
| Any other `ia` operation | `ia-cli` |
|
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Catch up on one client — build state, then risks and drift worst-first, then how to move forward
|
|
3
|
+
argument-hint: <client-slug> (or blank inside a clients/client-<slug>/ repo)
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
Run the `client-latest` skill for: **$ARGUMENTS**
|
|
7
|
+
|
|
8
|
+
If `$ARGUMENTS` is empty, resolve the client from the current directory. If
|
|
9
|
+
it is a company name rather than a slug, resolve it through
|
|
10
|
+
`team-clients/clients/*/PROFILE.md` and ask when two clients match.
|
|
11
|
+
|
|
12
|
+
Follow `skills/client-latest/SKILL.md` exactly: the wider of the two window
|
|
13
|
+
anchors, the seven read steps in order, every drift check, the bulleted
|
|
14
|
+
state + ranked-table output shape, and then the CTA — asked only when the
|
|
15
|
+
drift or risks/next table actually has rows; say the repo's clean and stop
|
|
16
|
+
otherwise. Gathering the brief writes nothing. Acting on a CTA choice stops
|
|
17
|
+
in the working tree: no commit, no push, and shared surfaces (Linear, n8n,
|
|
18
|
+
Airtable, Drive, Slack) are proposed, never changed.
|
|
@@ -0,0 +1,235 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: cloud-devops
|
|
3
|
+
description: "Cloud infrastructure and DevOps workflow covering AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring, and cloud-native development."
|
|
4
|
+
category: workflow-bundle
|
|
5
|
+
risk: safe
|
|
6
|
+
source: personal
|
|
7
|
+
date_added: "2026-02-27"
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
# Cloud/DevOps Workflow Bundle
|
|
11
|
+
|
|
12
|
+
## Overview
|
|
13
|
+
|
|
14
|
+
Comprehensive cloud and DevOps workflow for infrastructure provisioning, container orchestration, CI/CD pipelines, monitoring, and cloud-native application development.
|
|
15
|
+
|
|
16
|
+
## When to Use This Workflow
|
|
17
|
+
|
|
18
|
+
Use this workflow when:
|
|
19
|
+
- Setting up cloud infrastructure
|
|
20
|
+
- Implementing CI/CD pipelines
|
|
21
|
+
- Deploying Kubernetes applications
|
|
22
|
+
- Configuring monitoring and observability
|
|
23
|
+
- Managing cloud costs
|
|
24
|
+
- Implementing DevOps practices
|
|
25
|
+
|
|
26
|
+
## Workflow Phases
|
|
27
|
+
|
|
28
|
+
### Phase 1: Cloud Infrastructure Setup
|
|
29
|
+
|
|
30
|
+
#### Skills to Invoke
|
|
31
|
+
- `cloud-architect` - Cloud architecture
|
|
32
|
+
- `aws-skills` - AWS development
|
|
33
|
+
- `azure-functions` - Azure development
|
|
34
|
+
- `gcp-cloud-run` - GCP development
|
|
35
|
+
- `terraform-skill` - Terraform IaC
|
|
36
|
+
- `terraform-specialist` - Advanced Terraform
|
|
37
|
+
|
|
38
|
+
#### Actions
|
|
39
|
+
1. Design cloud architecture
|
|
40
|
+
2. Set up accounts and billing
|
|
41
|
+
3. Configure networking
|
|
42
|
+
4. Provision resources
|
|
43
|
+
5. Set up IAM
|
|
44
|
+
|
|
45
|
+
#### Copy-Paste Prompts
|
|
46
|
+
```
|
|
47
|
+
Use @cloud-architect to design multi-cloud architecture
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
```
|
|
51
|
+
Use @terraform-skill to provision AWS infrastructure
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
### Phase 2: Container Orchestration
|
|
55
|
+
|
|
56
|
+
#### Skills to Invoke
|
|
57
|
+
- `kubernetes-architect` - Kubernetes architecture
|
|
58
|
+
- `docker-expert` - Docker containerization
|
|
59
|
+
- `helm-chart-scaffolding` - Helm charts
|
|
60
|
+
- `k8s-manifest-generator` - K8s manifests
|
|
61
|
+
- `k8s-security-policies` - K8s security
|
|
62
|
+
|
|
63
|
+
#### Actions
|
|
64
|
+
1. Design container architecture
|
|
65
|
+
2. Create Dockerfiles
|
|
66
|
+
3. Build container images
|
|
67
|
+
4. Write K8s manifests
|
|
68
|
+
5. Deploy to cluster
|
|
69
|
+
6. Configure networking
|
|
70
|
+
|
|
71
|
+
#### Copy-Paste Prompts
|
|
72
|
+
```
|
|
73
|
+
Use @kubernetes-architect to design K8s architecture
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
```
|
|
77
|
+
Use @docker-expert to containerize application
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
```
|
|
81
|
+
Use @helm-chart-scaffolding to create Helm chart
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
### Phase 3: CI/CD Implementation
|
|
85
|
+
|
|
86
|
+
#### Skills to Invoke
|
|
87
|
+
- `deployment-engineer` - Deployment engineering
|
|
88
|
+
- `cicd-automation-workflow-automate` - CI/CD automation
|
|
89
|
+
- `github-actions-templates` - GitHub Actions
|
|
90
|
+
- `gitlab-ci-patterns` - GitLab CI
|
|
91
|
+
- `deployment-pipeline-design` - Pipeline design
|
|
92
|
+
|
|
93
|
+
#### Actions
|
|
94
|
+
1. Design deployment pipeline
|
|
95
|
+
2. Configure build automation
|
|
96
|
+
3. Set up test automation
|
|
97
|
+
4. Configure deployment stages
|
|
98
|
+
5. Implement rollback strategies
|
|
99
|
+
6. Set up notifications
|
|
100
|
+
|
|
101
|
+
#### Copy-Paste Prompts
|
|
102
|
+
```
|
|
103
|
+
Use @cicd-automation-workflow-automate to set up CI/CD pipeline
|
|
104
|
+
```
|
|
105
|
+
|
|
106
|
+
```
|
|
107
|
+
Use @github-actions-templates to create GitHub Actions workflow
|
|
108
|
+
```
|
|
109
|
+
|
|
110
|
+
### Phase 4: Monitoring and Observability
|
|
111
|
+
|
|
112
|
+
#### Skills to Invoke
|
|
113
|
+
- `observability-engineer` - Observability engineering
|
|
114
|
+
- `grafana-dashboards` - Grafana dashboards
|
|
115
|
+
- `prometheus-configuration` - Prometheus setup
|
|
116
|
+
- `datadog-automation` - Datadog integration
|
|
117
|
+
- `sentry-automation` - Sentry error tracking
|
|
118
|
+
|
|
119
|
+
#### Actions
|
|
120
|
+
1. Design monitoring strategy
|
|
121
|
+
2. Set up metrics collection
|
|
122
|
+
3. Configure log aggregation
|
|
123
|
+
4. Implement distributed tracing
|
|
124
|
+
5. Create dashboards
|
|
125
|
+
6. Set up alerts
|
|
126
|
+
|
|
127
|
+
#### Copy-Paste Prompts
|
|
128
|
+
```
|
|
129
|
+
Use @observability-engineer to set up observability stack
|
|
130
|
+
```
|
|
131
|
+
|
|
132
|
+
```
|
|
133
|
+
Use @grafana-dashboards to create monitoring dashboards
|
|
134
|
+
```
|
|
135
|
+
|
|
136
|
+
### Phase 5: Cloud Security
|
|
137
|
+
|
|
138
|
+
#### Skills to Invoke
|
|
139
|
+
- `cloud-penetration-testing` - Cloud pentesting
|
|
140
|
+
- `aws-penetration-testing` - AWS security
|
|
141
|
+
- `k8s-security-policies` - K8s security
|
|
142
|
+
- `secrets-management` - Secrets management
|
|
143
|
+
- `mtls-configuration` - mTLS setup
|
|
144
|
+
|
|
145
|
+
#### Actions
|
|
146
|
+
1. Assess cloud security
|
|
147
|
+
2. Configure security groups
|
|
148
|
+
3. Set up secrets management
|
|
149
|
+
4. Implement network policies
|
|
150
|
+
5. Configure encryption
|
|
151
|
+
6. Set up audit logging
|
|
152
|
+
|
|
153
|
+
#### Copy-Paste Prompts
|
|
154
|
+
```
|
|
155
|
+
Use @cloud-penetration-testing to assess cloud security
|
|
156
|
+
```
|
|
157
|
+
|
|
158
|
+
```
|
|
159
|
+
Use @secrets-management to configure secrets
|
|
160
|
+
```
|
|
161
|
+
|
|
162
|
+
### Phase 6: Cost Optimization
|
|
163
|
+
|
|
164
|
+
#### Skills to Invoke
|
|
165
|
+
- `cost-optimization` - Cloud cost optimization
|
|
166
|
+
- `database-cloud-optimization-cost-optimize` - Database cost optimization
|
|
167
|
+
|
|
168
|
+
#### Actions
|
|
169
|
+
1. Analyze cloud spending
|
|
170
|
+
2. Identify optimization opportunities
|
|
171
|
+
3. Right-size resources
|
|
172
|
+
4. Implement auto-scaling
|
|
173
|
+
5. Use reserved instances
|
|
174
|
+
6. Set up cost alerts
|
|
175
|
+
|
|
176
|
+
#### Copy-Paste Prompts
|
|
177
|
+
```
|
|
178
|
+
Use @cost-optimization to reduce cloud costs
|
|
179
|
+
```
|
|
180
|
+
|
|
181
|
+
### Phase 7: Disaster Recovery
|
|
182
|
+
|
|
183
|
+
#### Skills to Invoke
|
|
184
|
+
- `incident-responder` - Incident response
|
|
185
|
+
- `incident-runbook-templates` - Runbook creation
|
|
186
|
+
- `postmortem-writing` - Postmortem documentation
|
|
187
|
+
|
|
188
|
+
#### Actions
|
|
189
|
+
1. Design DR strategy
|
|
190
|
+
2. Set up backups
|
|
191
|
+
3. Create runbooks
|
|
192
|
+
4. Test failover
|
|
193
|
+
5. Document procedures
|
|
194
|
+
6. Train team
|
|
195
|
+
|
|
196
|
+
#### Copy-Paste Prompts
|
|
197
|
+
```
|
|
198
|
+
Use @incident-runbook-templates to create runbooks
|
|
199
|
+
```
|
|
200
|
+
|
|
201
|
+
## Cloud Provider Workflows
|
|
202
|
+
|
|
203
|
+
### AWS
|
|
204
|
+
```
|
|
205
|
+
Skills: aws-skills, aws-serverless, aws-penetration-testing
|
|
206
|
+
Services: EC2, Lambda, S3, RDS, ECS, EKS
|
|
207
|
+
```
|
|
208
|
+
|
|
209
|
+
### Azure
|
|
210
|
+
```
|
|
211
|
+
Skills: azure-functions, azure-ai-projects-py, azure-monitor-opentelemetry-py
|
|
212
|
+
Services: Functions, App Service, AKS, Cosmos DB
|
|
213
|
+
```
|
|
214
|
+
|
|
215
|
+
### GCP
|
|
216
|
+
```
|
|
217
|
+
Skills: gcp-cloud-run
|
|
218
|
+
Services: Cloud Run, GKE, Cloud Functions, BigQuery
|
|
219
|
+
```
|
|
220
|
+
|
|
221
|
+
## Quality Gates
|
|
222
|
+
|
|
223
|
+
- [ ] Infrastructure provisioned
|
|
224
|
+
- [ ] CI/CD pipeline working
|
|
225
|
+
- [ ] Monitoring configured
|
|
226
|
+
- [ ] Security measures in place
|
|
227
|
+
- [ ] Cost optimization applied
|
|
228
|
+
- [ ] DR procedures documented
|
|
229
|
+
|
|
230
|
+
## Related Workflow Bundles
|
|
231
|
+
|
|
232
|
+
- `development` - Application development
|
|
233
|
+
- `security-audit` - Security testing
|
|
234
|
+
- `database` - Database operations
|
|
235
|
+
- `testing-qa` - Testing workflows
|