init-workspace

Name: init-workspace
Author: gtrabanco

34installs2forks

How to install init-workspace?

gtrabanco/agentic-workflow/init-workspace

$npx -y skills add gtrabanco/agentic-workflow --skill init-workspace

Installs into the current project.

Summary

Bootstrap a project's way of working: fetch the agentic-workflow documentation scaffold (template/) and adapt it to THIS project by interview — fill the CLAUDE.md documentation map, gate commands and architecture, prune doc folders that don't apply, keep the SPEC/feature/fix and

Files · 1

View on GitHub

SKILL.md

1	# Init Workspace
2
3	Turn an empty or existing repo into one that works with the agentic workflow:
4	copy the generic scaffold, then tailor it to this project instead of leaving
5	raw placeholders.
6
7	## Turn contract — verify before ending the turn
8
9	```
10	✓ The adapted scaffold is written (or the merge/abort decision was asked) and remaining placeholders are listed
11	✓ Nothing was installed or overwritten without an explicit yes
12	✓ Artifact language: explicit user instruction > the project's declared docs language > English. The CONVERSATION language never decides — a Spanish prompt still produces English PRs/issues/commits/SPECs unless one of the first two says otherwise
13	✓ The closing `→ Next:` block is printed as the ABSOLUTE last output
14	```
15
16	About to end the turn with any box unchecked? The turn is NOT done — complete
17	the missing box first (weak models drop end-of-document duties; this list is
18	first on purpose).
19
20	## When to use
21
22	- Setting up a repo to use these skills and you want the documentation substrate
23	(`CLAUDE.md` + `docs/` map + templates) adapted to the project, not just copied.
24	- Prefer this over a static `npx degit gtrabanco/agentic-workflow/template` when you
25	want the gate commands, architecture, and doc domains filled in by interview.
26
27	## Step 0 — Discover the project (always first)
28
29	Inspect the target dir (`[target-dir]`, default cwd) before touching anything:
30
31	- Existing `CLAUDE.md` / `AGENTS.md` / `docs/` / `.github/`? If so, **do not
32	clobber — check first whether it's an agentic-workflow scaffold**
33	(marker: `CLAUDE.md` present and either `docs/features/ROADMAP.md` or a
34	`docs/workflow/` dir). If both markers are present, offer upgrade as the
35	default action, alongside merge / adapt-in-place / abort — see **Upgrade
36	mode** below. If `CLAUDE.md`/`docs/` exist but the markers are absent (a
37	foreign scaffold), stay in bootstrap and ask merge / adapt in place / abort
38	as before.
39	- Detect the stack from manifests (`package.json`, `pyproject.toml`, `go.mod`,
40	`Cargo.toml`, `Gemfile`, …) to propose gate commands and naming conventions.
41	- Note the git state (is it a repo, what's the default branch, and the **remote
42	URL → forge**: github.com → GitHub/`gh`, gitlab → GitLab/`glab`, else ask).
43
44	## Process
45
46	1. Preflight. Confirm the target dir and the discovery findings. If scaffold
47	files already exist, get an explicit decision before overwriting.
48	2. Fetch the template. `npx degit gtrabanco/agentic-workflow/template <dir>`
49	(into the target if empty, else a temp dir to merge from). **`degit` can't read
50	a private repo — it fails, or in `--mode=git` silently leaves an empty dir; for
51	a private source, `git clone` via SSH and copy the `template/` subtree instead.**
52	3. Interview to adapt — small batched rounds, each with a recommended default
53	drawn from Step 0; skip whatever discovery already answers:
54	- Project — name + one-line purpose.
55	- Gate — dev / build / test commands and the verification gate (proposed
56	from the detected stack; confirm).
57	- Forge — issue/PR tracker + CLI (proposed from the remote URL; confirm)
58	→ recorded in the Workflow conventions Forge line.
59	- Git workflow — how parallel work is handled: branches (default —
60	one active unit at a time, sequential, plain `git switch -c`) or
61	worktrees (parallel units in separate checkouts; only if the user's
62	agent/tooling manages them). Recorded in the Workflow conventions
63	Git workflow line; every skill that creates

People who liked this also viewed

6 picks

Type

init-workspace

34installs2forks

View on GitHub

How to install init-workspace?

gtrabanco/agentic-workflow/init-workspace

$npx -y skills add gtrabanco/agentic-workflow --skill init-workspace

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Init Workspace
2
3	Turn an empty or existing repo into one that works with the agentic workflow:
4	copy the generic scaffold, then tailor it to this project instead of leaving
5	raw placeholders.
6
7	## Turn contract — verify before ending the turn
8
9	```
10	✓ The adapted scaffold is written (or the merge/abort decision was asked) and remaining placeholders are listed
11	✓ Nothing was installed or overwritten without an explicit yes
12	✓ Artifact language: explicit user instruction > the project's declared docs language > English. The CONVERSATION language never decides — a Spanish prompt still produces English PRs/issues/commits/SPECs unless one of the first two says otherwise
13	✓ The closing `→ Next:` block is printed as the ABSOLUTE last output
14	```
15
16	About to end the turn with any box unchecked? The turn is NOT done — complete
17	the missing box first (weak models drop end-of-document duties; this list is
18	first on purpose).
19
20	## When to use
21
22	- Setting up a repo to use these skills and you want the documentation substrate
23	(`CLAUDE.md` + `docs/` map + templates) adapted to the project, not just copied.
24	- Prefer this over a static `npx degit gtrabanco/agentic-workflow/template` when you
25	want the gate commands, architecture, and doc domains filled in by interview.
26
27	## Step 0 — Discover the project (always first)
28
29	Inspect the target dir (`[target-dir]`, default cwd) before touching anything:
30
31	- Existing `CLAUDE.md` / `AGENTS.md` / `docs/` / `.github/`? If so, **do not
32	clobber — check first whether it's an agentic-workflow scaffold**
33	(marker: `CLAUDE.md` present and either `docs/features/ROADMAP.md` or a
34	`docs/workflow/` dir). If both markers are present, offer upgrade as the
35	default action, alongside merge / adapt-in-place / abort — see **Upgrade
36	mode** below. If `CLAUDE.md`/`docs/` exist but the markers are absent (a
37	foreign scaffold), stay in bootstrap and ask merge / adapt in place / abort
38	as before.
39	- Detect the stack from manifests (`package.json`, `pyproject.toml`, `go.mod`,
40	`Cargo.toml`, `Gemfile`, …) to propose gate commands and naming conventions.
41	- Note the git state (is it a repo, what's the default branch, and the **remote
42	URL → forge**: github.com → GitHub/`gh`, gitlab → GitLab/`glab`, else ask).
43
44	## Process
45
46	1. Preflight. Confirm the target dir and the discovery findings. If scaffold
47	files already exist, get an explicit decision before overwriting.
48	2. Fetch the template. `npx degit gtrabanco/agentic-workflow/template <dir>`
49	(into the target if empty, else a temp dir to merge from). **`degit` can't read
50	a private repo — it fails, or in `--mode=git` silently leaves an empty dir; for
51	a private source, `git clone` via SSH and copy the `template/` subtree instead.**
52	3. Interview to adapt — small batched rounds, each with a recommended default
53	drawn from Step 0; skip whatever discovery already answers:
54	- Project — name + one-line purpose.
55	- Gate — dev / build / test commands and the verification gate (proposed
56	from the detected stack; confirm).
57	- Forge — issue/PR tracker + CLI (proposed from the remote URL; confirm)
58	→ recorded in the Workflow conventions Forge line.
59	- Git workflow — how parallel work is handled: branches (default —
60	one active unit at a time, sequential, plain `git switch -c`) or
61	worktrees (parallel units in separate checkouts; only if the user's
62	agent/tooling manages them). Recorded in the Workflow conventions
63	Git workflow line; every skill that creates

People who liked this also viewed

6 picks

Type