co-math-init

Name: co-math-init
Author: morankor

57stars19forks

How to install co-math-init?

morankor/theorist-toolbox/co-math-init

$npx -y skills add morankor/theorist-toolbox --skill co-math-init

Installs into the current project.

Summary

Initialize a disciplined AI co-mathematician research project for Codex. Use when starting a math or economic theory investigation that needs goals.md, paper.tex, workstreams, decisions, reviewer approvals, strict no-hand-waving proof tracking, Lean/code workstreams, or a durable

Files · 1

View on GitHub

SKILL.md

1	# Co-Math Init
2
3	Create a local research project modeled on the Theorist Toolbox co-math workflow. The project keeps a living `paper.tex`, explicit goals, append-only decisions, workstream reports, reviewer approvals, failed explorations, and open proof obligations.
4
5	Strict mode is the default. In strict mode, every proof gap must be marked with `\unproven{...}` until reviewed or machine-checked.
6
7	## Inputs
8
9	Gather or infer:
10
11	- project name: lowercase kebab-case,
12	- research question: one or two sentences,
13	- parent directory: default to the current working directory,
14	- strict mode: default `true`; only set `false` if the user explicitly asks for pragmatic mode.
15
16	If the project name is missing, derive a short kebab-case name from the research question. If the research question is missing, ask for it.
17
18	## Create The Project
19
20	Run the bundled script from the skill directory:
21
22	```bash
23	python3 scripts/init_co_math_project.py \
24	--name <project-name> \
25	--question "<research question>" \
26	--parent <parent-directory>
27	```
28
29	For pragmatic mode:
30
31	```bash
32	python3 scripts/init_co_math_project.py \
33	--name <project-name> \
34	--question "<research question>" \
35	--parent <parent-directory> \
36	--pragmatic
37	```
38
39	The script creates:
40
41	```text
42	paper.tex
43	goals.md
44	decisions.md
45	README.md
46	AGENTS.md
47	co-math-config.json
48	workstreams/.gitkeep
49	references/.gitkeep
50	failed-explorations/.gitkeep
51	.co-math/approvals/.gitkeep
52	.co-math/workstream-registry.json
53	```
54
55	## After Initialization
56
57	Tell the user:
58
59	- the absolute path of the created project,
60	- `goals.md` is where the research question and sub-goals are refined,
61	- no workstream should start until goals are approved,
62	- `paper.tex` is the living paper,
63	- `workstreams/` will hold one directory per proof, literature, code, Lean, or readability task,
64	- `.co-math/approvals/` is the reviewer gate,
65	- `failed-explorations/` is intentionally durable and should not be cleaned away.
66
67	If the package's Codex custom agents are installed, suggest starting with the `co-math-project-coordinator` agent. If not, Codex can still run the workflow manually using the project files and the role profiles in this package.
68
69	## What Not To Do
70
71	- Do not start proving immediately during initialization.
72	- Do not mark goals approved on behalf of the user.
73	- Do not disable strict mode unless the user explicitly asks.
74	- Do not remove `\unproven{}` obligations to make the paper look cleaner.

People who liked this also viewed

6 picks

Type

co-math-init

57stars19forks

View on GitHub

How to install co-math-init?

morankor/theorist-toolbox/co-math-init

$npx -y skills add morankor/theorist-toolbox --skill co-math-init

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Co-Math Init
2
3	Create a local research project modeled on the Theorist Toolbox co-math workflow. The project keeps a living `paper.tex`, explicit goals, append-only decisions, workstream reports, reviewer approvals, failed explorations, and open proof obligations.
4
5	Strict mode is the default. In strict mode, every proof gap must be marked with `\unproven{...}` until reviewed or machine-checked.
6
7	## Inputs
8
9	Gather or infer:
10
11	- project name: lowercase kebab-case,
12	- research question: one or two sentences,
13	- parent directory: default to the current working directory,
14	- strict mode: default `true`; only set `false` if the user explicitly asks for pragmatic mode.
15
16	If the project name is missing, derive a short kebab-case name from the research question. If the research question is missing, ask for it.
17
18	## Create The Project
19
20	Run the bundled script from the skill directory:
21
22	```bash
23	python3 scripts/init_co_math_project.py \
24	--name <project-name> \
25	--question "<research question>" \
26	--parent <parent-directory>
27	```
28
29	For pragmatic mode:
30
31	```bash
32	python3 scripts/init_co_math_project.py \
33	--name <project-name> \
34	--question "<research question>" \
35	--parent <parent-directory> \
36	--pragmatic
37	```
38
39	The script creates:
40
41	```text
42	paper.tex
43	goals.md
44	decisions.md
45	README.md
46	AGENTS.md
47	co-math-config.json
48	workstreams/.gitkeep
49	references/.gitkeep
50	failed-explorations/.gitkeep
51	.co-math/approvals/.gitkeep
52	.co-math/workstream-registry.json
53	```
54
55	## After Initialization
56
57	Tell the user:
58
59	- the absolute path of the created project,
60	- `goals.md` is where the research question and sub-goals are refined,
61	- no workstream should start until goals are approved,
62	- `paper.tex` is the living paper,
63	- `workstreams/` will hold one directory per proof, literature, code, Lean, or readability task,
64	- `.co-math/approvals/` is the reviewer gate,
65	- `failed-explorations/` is intentionally durable and should not be cleaned away.
66
67	If the package's Codex custom agents are installed, suggest starting with the `co-math-project-coordinator` agent. If not, Codex can still run the workflow manually using the project files and the role profiles in this package.
68
69	## What Not To Do
70
71	- Do not start proving immediately during initialization.
72	- Do not mark goals approved on behalf of the user.
73	- Do not disable strict mode unless the user explicitly asks.
74	- Do not remove `\unproven{}` obligations to make the paper look cleaner.

People who liked this also viewed

6 picks

Type