project-dossier

Name: project-dossier
Author: AlpacaLabsLLC

260stars54forks

How to install project-dossier?

alpacalabsllc/skills-for-architects/project-dossier

$npx -y skills add AlpacaLabsLLC/skills-for-architects --skill project-dossier

Installs into the current project.

Summary

Create or update the project dossier — a PROJECT.md file in the working directory holding persistent project facts (identity, site, zoning, program, code edition) plus an index of decisions. Use when starting a project, when the user says "set up the project" or "remember this fo

Files · 1

View on GitHub

SKILL.md

1	# /project-dossier — Project Facts File
2
3	You maintain `PROJECT.md`: a single file at the project root that holds the durable facts of an architecture project, so no skill re-derives what's already known and the whole team sees the same state.
4
5	The dossier is the facts layer. The reasoning layer — why a choice was made — lives in `decisions/` via `/decision`. Don't mix them: PROJECT.md says what is; a decision record says why it is.
6
7	## Usage
8
9	```
10	/project-dossier → show current dossier status (or offer to init)
11	/project-dossier init → create PROJECT.md, interview for the basics
12	/project-dossier update → reconcile the dossier with new facts from the conversation
13	```
14
15	## Hard rules
16
17	1. Every entry carries a source and a date. `FAR 6.02 (PLUTO, 2026-06-10)` — never an orphan number. If the user states a fact verbally, the source is `client, YYYY-MM-DD`.
18	2. Update in place, never duplicate. If a fact changes (re-run analysis, corrected input), replace the value and refresh the source/date. The dossier holds current state, not history — history is git's job.
19	3. Facts only. "Zoning district: R7A" belongs here. "We chose the UAP bonus over the contextual envelope" is a decision — propose `/decision` instead.
20	4. Project facts only. User preferences, workflow habits, and firm conventions do NOT belong in the dossier — Claude Code's own memory (CLAUDE.md, auto memory) handles those.
21
22	## On `init`
23
24	1. If `PROJECT.md` already exists, say so and switch to `update` mode.
25	2. Ask for whatever basics aren't already evident from the conversation (one question, grouped): project name, address, client, jurisdiction.
26	3. Write `PROJECT.md` from the template below, filling what you know, leaving the rest blank.
27	4. If the working directory is a git repo, suggest committing it: the dossier is meant to be shared with the team.
28
29	## On `update`
30
31	1. Read `PROJECT.md`.
32	2. Collect new facts from the current conversation (analysis results, corrected values, user statements).
33	3. Apply rule 2 — replace stale values in place, append genuinely new ones to the right section, each with source + date.
34	4. Show a short diff-style summary of what changed.
35
36	## Template
37
38	```markdown
39	# Project Dossier — {project name}
40
41	> Maintained by Architecture Studio skills and the project team.
42	> Every entry carries a source and a date. Facts only — rationale lives in the decisions/ directory.
43
44	## Identity
45
46	\| Field \| Value \|
47	\|-------\|-------\|
48	\| Project \| \|
49	\| Address / BBL \| \|
50	\| Client \| \|
51	\| Jurisdiction \| \|
52
53	## Site
54
55	<!-- site-planner skills append here: climate, flood, transit, demographics, context -->
56
57	## Zoning
58
59	<!-- zoning skills append here: district, FAR, envelope results, overlays, landmark status -->
60
61	## Program
62
63	<!-- programming skills append here: headcount, space program, occupant loads -->
64
65	## Code
66
67	\| Item \| Value \| Source \| Date \|
68	\|------\|-------\|--------\|------\|
69	\| Building code edition \| \| \| \|
70
71	## Decisions
72
73	<!-- maintained by /decision — do not edit by hand -->
74
75	\| # \| Decision \| Status \| Date \|
76	\|---\|----------\|--------\|------\|
77	```
78
79	## How other skills use the dossier
80
81	Analysis skills in this marketplace check for `PROJECT.md` before fetching (don't re-derive what's on file) and append their key findings after completing. That behavior lives in each skill — your job here is only init, update, and keeping the file well-formed.
82
83	## Edge cases
84
85	\| Situation \| Handling \|
86	\|-----------\|----------\|
87	\| `PROJECT.md` exists but malformed / hand-edited \| Preserve all content; reorganize into template sections; say what moved \|
88	\| Facts conflict (dossier says X, user says Y) \| Ask once; the answer wins; update with new source + date \|
89	\| No project context at all, user just ran `/project-dossier` \| Show usage and ask if they want `init` \|
90	\| Multiple projects in one directory \| One dossier per directory — suggest separate working directories \|

People who liked this also viewed

6 picks

Type

project-dossier

260stars54forks

View on GitHub

How to install project-dossier?

alpacalabsllc/skills-for-architects/project-dossier

$npx -y skills add AlpacaLabsLLC/skills-for-architects --skill project-dossier

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# /project-dossier — Project Facts File
2
3	You maintain `PROJECT.md`: a single file at the project root that holds the durable facts of an architecture project, so no skill re-derives what's already known and the whole team sees the same state.
4
5	The dossier is the facts layer. The reasoning layer — why a choice was made — lives in `decisions/` via `/decision`. Don't mix them: PROJECT.md says what is; a decision record says why it is.
6
7	## Usage
8
9	```
10	/project-dossier → show current dossier status (or offer to init)
11	/project-dossier init → create PROJECT.md, interview for the basics
12	/project-dossier update → reconcile the dossier with new facts from the conversation
13	```
14
15	## Hard rules
16
17	1. Every entry carries a source and a date. `FAR 6.02 (PLUTO, 2026-06-10)` — never an orphan number. If the user states a fact verbally, the source is `client, YYYY-MM-DD`.
18	2. Update in place, never duplicate. If a fact changes (re-run analysis, corrected input), replace the value and refresh the source/date. The dossier holds current state, not history — history is git's job.
19	3. Facts only. "Zoning district: R7A" belongs here. "We chose the UAP bonus over the contextual envelope" is a decision — propose `/decision` instead.
20	4. Project facts only. User preferences, workflow habits, and firm conventions do NOT belong in the dossier — Claude Code's own memory (CLAUDE.md, auto memory) handles those.
21
22	## On `init`
23
24	1. If `PROJECT.md` already exists, say so and switch to `update` mode.
25	2. Ask for whatever basics aren't already evident from the conversation (one question, grouped): project name, address, client, jurisdiction.
26	3. Write `PROJECT.md` from the template below, filling what you know, leaving the rest blank.
27	4. If the working directory is a git repo, suggest committing it: the dossier is meant to be shared with the team.
28
29	## On `update`
30
31	1. Read `PROJECT.md`.
32	2. Collect new facts from the current conversation (analysis results, corrected values, user statements).
33	3. Apply rule 2 — replace stale values in place, append genuinely new ones to the right section, each with source + date.
34	4. Show a short diff-style summary of what changed.
35
36	## Template
37
38	```markdown
39	# Project Dossier — {project name}
40
41	> Maintained by Architecture Studio skills and the project team.
42	> Every entry carries a source and a date. Facts only — rationale lives in the decisions/ directory.
43
44	## Identity
45
46	\| Field \| Value \|
47	\|-------\|-------\|
48	\| Project \| \|
49	\| Address / BBL \| \|
50	\| Client \| \|
51	\| Jurisdiction \| \|
52
53	## Site
54
55	<!-- site-planner skills append here: climate, flood, transit, demographics, context -->
56
57	## Zoning
58
59	<!-- zoning skills append here: district, FAR, envelope results, overlays, landmark status -->
60
61	## Program
62
63	<!-- programming skills append here: headcount, space program, occupant loads -->
64
65	## Code
66
67	\| Item \| Value \| Source \| Date \|
68	\|------\|-------\|--------\|------\|
69	\| Building code edition \| \| \| \|
70
71	## Decisions
72
73	<!-- maintained by /decision — do not edit by hand -->
74
75	\| # \| Decision \| Status \| Date \|
76	\|---\|----------\|--------\|------\|
77	```
78
79	## How other skills use the dossier
80
81	Analysis skills in this marketplace check for `PROJECT.md` before fetching (don't re-derive what's on file) and append their key findings after completing. That behavior lives in each skill — your job here is only init, update, and keeping the file well-formed.
82
83	## Edge cases
84
85	\| Situation \| Handling \|
86	\|-----------\|----------\|
87	\| `PROJECT.md` exists but malformed / hand-edited \| Preserve all content; reorganize into template sections; say what moved \|
88	\| Facts conflict (dossier says X, user says Y) \| Ask once; the answer wins; update with new source + date \|
89	\| No project context at all, user just ran `/project-dossier` \| Show usage and ask if they want `init` \|
90	\| Multiple projects in one directory \| One dossier per directory — suggest separate working directories \|

People who liked this also viewed

6 picks

Type