oh-my-pm 1.0.0 → 1.0.1

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/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Oh My PM
2
2
 
3
- Oh My PM installs a Product Management agent team inside a project. The team produces PRD, TRD, UX flows, database design, execution planning, and an interoperable contract named `.parkops/pm_manifest.json`.
3
+ Oh My PM installs a Product Management agent team inside a project. The team produces PRD, TRD, UX flows, database design, execution planning, and an interoperable contract named `.pm/pm_manifest.json`.
4
4
 
5
5
  The package is designed for `bunx oh-my-pm` usage and can generate platform-specific outputs for OpenCode, Claude Code, OpenAI Agents SDK, and generic Markdown-based LLM workflows.
6
6
 
@@ -18,7 +18,7 @@ The package is designed for `bunx oh-my-pm` usage and can generate platform-spec
18
18
 
19
19
  - **Lane specialization**: every agent owns a strict domain and JC delegates with complete context.
20
20
  - **Verification before completion**: no agent reports completion without concrete evidence.
21
- - **Contract-based communication**: Oh My PM and Dev-Harness communicate only through `.parkops/pm_manifest.json`.
21
+ - **Contract-based communication**: Oh My PM and Dev-Harness communicate only through `.pm/pm_manifest.json`.
22
22
  - **Full context on delegation**: every handoff includes paths, decisions, constraints, and exit criteria.
23
23
  - **Technical honesty**: ambiguity and contradiction become blockers instead of guesses.
24
24
 
@@ -26,7 +26,7 @@ The package is designed for `bunx oh-my-pm` usage and can generate platform-spec
26
26
 
27
27
  | Agent | Role | Artifacts |
28
28
  | --- | --- | --- |
29
- | JC | Discovery and approval orchestrator | `.parkops/pm_manifest.json`, routing, approval notes |
29
+ | JC | Discovery and approval orchestrator | `.pm/pm_manifest.json`, routing, approval notes |
30
30
  | Hammurabi | PRD and product rules | `docs/prd.md` |
31
31
  | DaVinci | UX, UI flows, and Mermaid | `docs/flows/*.md` |
32
32
  | Ada | TRD, API, data, and schemas | `docs/trd.md`, `docs/db-schema.md` |
@@ -52,8 +52,8 @@ AGENTS.md
52
52
  .opencode/skills/suntzu/SKILL.md
53
53
  .opencode/skills/oh-my-pm/SKILL.md
54
54
  oh-my-pm.json
55
- .parkops/pm_manifest.json
56
- .parkops/schemas/pm-manifest-schema.json
55
+ .pm/pm_manifest.json
56
+ .pm/schemas/pm-manifest-schema.json
57
57
  ```
58
58
 
59
59
  The generated `opencode.jsonc` loads the runtime plugin:
@@ -94,6 +94,7 @@ Existing files are backed up with `.oh-my-pm.backup` before replacement or merge
94
94
  ## Optional platform outputs
95
95
 
96
96
  ```bash
97
+ bunx oh-my-pm install --opencode
97
98
  bunx oh-my-pm install --claude
98
99
  bunx oh-my-pm install --openai
99
100
  bunx oh-my-pm install --generic
@@ -118,7 +119,7 @@ bunx oh-my-pm generate generic
118
119
  5. Ada writes TRD, API, and database design.
119
120
  6. SunTzu builds the execution DAG and updates the manifest.
120
121
  7. JC validates the contract and asks for approval.
121
- 8. Dev-Harness consumes `.parkops/pm_manifest.json` and writes blockers back into that file.
122
+ 8. Dev-Harness consumes `.pm/pm_manifest.json` and writes blockers back into that file.
122
123
 
123
124
  ## Dev-Harness contract
124
125
 
@@ -51,7 +51,7 @@ Durable artifacts: `docs/trd.md` and `docs/db-schema.md`.
51
51
 
52
52
  - Lane specialization: this agent does not invade other domains.
53
53
  - Verification before completion: each delivery includes reproducible evidence.
54
- - Contract-based communication: `.parkops/pm_manifest.json` is the contract.
54
+ - Contract-based communication: `.pm/pm_manifest.json` is the contract.
55
55
  - Full context on delegation: every handoff includes paths, decisions, and constraints.
56
56
  - Technical honesty: ambiguity or contradiction becomes a blocker.
57
57
 
@@ -64,6 +64,6 @@ Durable artifacts: `docs/trd.md` and `docs/db-schema.md`.
64
64
 
65
65
  ## Cross-reference requirements
66
66
 
67
- - Every artifact must appear in `.parkops/pm_manifest.json`.
67
+ - Every artifact must appear in `.pm/pm_manifest.json`.
68
68
  - Every DAG task must point to a PRD, TRD, flow, or execution-plan section.
69
69
  - Every decision must record rationale and alternatives considered.
@@ -49,7 +49,7 @@ Durable artifact: `docs/flows/main-flow.md`.
49
49
 
50
50
  - Lane specialization: this agent does not invade other domains.
51
51
  - Verification before completion: each delivery includes reproducible evidence.
52
- - Contract-based communication: `.parkops/pm_manifest.json` is the contract.
52
+ - Contract-based communication: `.pm/pm_manifest.json` is the contract.
53
53
  - Full context on delegation: every handoff includes paths, decisions, and constraints.
54
54
  - Technical honesty: ambiguity or contradiction becomes a blocker.
55
55
 
@@ -62,6 +62,6 @@ Durable artifact: `docs/flows/main-flow.md`.
62
62
 
63
63
  ## Cross-reference requirements
64
64
 
65
- - Every artifact must appear in `.parkops/pm_manifest.json`.
65
+ - Every artifact must appear in `.pm/pm_manifest.json`.
66
66
  - Every DAG task must point to a PRD, TRD, flow, or execution-plan section.
67
67
  - Every decision must record rationale and alternatives considered.
@@ -51,7 +51,7 @@ Durable artifact: `docs/prd.md`.
51
51
 
52
52
  - Lane specialization: this agent does not invade other domains.
53
53
  - Verification before completion: each delivery includes reproducible evidence.
54
- - Contract-based communication: `.parkops/pm_manifest.json` is the contract.
54
+ - Contract-based communication: `.pm/pm_manifest.json` is the contract.
55
55
  - Full context on delegation: every handoff includes paths, decisions, and constraints.
56
56
  - Technical honesty: ambiguity or contradiction becomes a blocker.
57
57
 
@@ -64,6 +64,6 @@ Durable artifact: `docs/prd.md`.
64
64
 
65
65
  ## Cross-reference requirements
66
66
 
67
- - Every artifact must appear in `.parkops/pm_manifest.json`.
67
+ - Every artifact must appear in `.pm/pm_manifest.json`.
68
68
  - Every DAG task must point to a PRD, TRD, flow, or execution-plan section.
69
69
  - Every decision must record rationale and alternatives considered.
@@ -9,7 +9,7 @@ JC represents strategic orchestration: listening, synthesis, and deciding when t
9
9
  - Run product discovery.
10
10
  - Define scope, constraints, risks, and approval criteria.
11
11
  - Delegate to Hammurabi, DaVinci, Ada, and SunTzu with complete context.
12
- - Validate `.parkops/pm_manifest.json` before asking for approval.
12
+ - Validate `.pm/pm_manifest.json` before asking for approval.
13
13
 
14
14
  ## Triggers EN
15
15
 
@@ -49,7 +49,7 @@ Durable artifact: `_workspace/jc/artifacts/discovery.md`.
49
49
 
50
50
  - Lane specialization: this agent does not invade other domains.
51
51
  - Verification before completion: each delivery includes reproducible evidence.
52
- - Contract-based communication: `.parkops/pm_manifest.json` is the contract.
52
+ - Contract-based communication: `.pm/pm_manifest.json` is the contract.
53
53
  - Full context on delegation: every handoff includes paths, decisions, and constraints.
54
54
  - Technical honesty: ambiguity or contradiction becomes a blocker.
55
55
 
@@ -62,6 +62,6 @@ Durable artifact: `_workspace/jc/artifacts/discovery.md`.
62
62
 
63
63
  ## Cross-reference requirements
64
64
 
65
- - Every artifact must appear in `.parkops/pm_manifest.json`.
65
+ - Every artifact must appear in `.pm/pm_manifest.json`.
66
66
  - Every DAG task must point to a PRD, TRD, flow, or execution-plan section.
67
67
  - Every decision must record rationale and alternatives considered.
@@ -7,7 +7,7 @@ SunTzu represents sequencing, terrain, and execution strategy. In Oh My PM, SunT
7
7
  ## Core responsibilities
8
8
 
9
9
  - Write `docs/execution-plan.md`.
10
- - Create `execution_dag.tasks` in `.parkops/pm_manifest.json`.
10
+ - Create `execution_dag.tasks` in `.pm/pm_manifest.json`.
11
11
  - Define dependencies, owners, and verification criteria.
12
12
  - Maintain blockers when a task is not honestly executable.
13
13
 
@@ -47,7 +47,7 @@ Durable artifact: `docs/execution-plan.md`.
47
47
 
48
48
  - Lane specialization: this agent does not invade other domains.
49
49
  - Verification before completion: each delivery includes reproducible evidence.
50
- - Contract-based communication: `.parkops/pm_manifest.json` is the contract.
50
+ - Contract-based communication: `.pm/pm_manifest.json` is the contract.
51
51
  - Full context on delegation: every handoff includes paths, decisions, and constraints.
52
52
  - Technical honesty: ambiguity or contradiction becomes a blocker.
53
53
 
@@ -60,6 +60,6 @@ Durable artifact: `docs/execution-plan.md`.
60
60
 
61
61
  ## Cross-reference requirements
62
62
 
63
- - Every artifact must appear in `.parkops/pm_manifest.json`.
63
+ - Every artifact must appear in `.pm/pm_manifest.json`.
64
64
  - Every DAG task must point to a PRD, TRD, flow, or execution-plan section.
65
65
  - Every decision must record rationale and alternatives considered.
@@ -6,7 +6,7 @@ Oh My PM is a project-level Product Management harness that installs agent instr
6
6
 
7
7
  | Component | Responsibility |
8
8
  | --- | --- |
9
- | CLI | Installs templates, initializes `.parkops/`, validates manifests. |
9
+ | CLI | Installs templates, initializes `.pm/`, validates manifests. |
10
10
  | OpenCode runtime plugin | Registers five PM agents through OpenCode `config.agent`. |
11
11
  | OpenCode templates | `SKILL.md` files for project-level routing and memory. |
12
12
  | Claude template | `CLAUDE.md` instructions for Task-based delegation. |
@@ -33,7 +33,7 @@ JC delegates by lane. Each specialist receives complete context and returns an a
33
33
 
34
34
  ## Contract model
35
35
 
36
- `.parkops/pm_manifest.json` is the only cross-system contract. It references all blueprints and stores DAG tasks, decisions, and blockers.
36
+ `.pm/pm_manifest.json` is the only cross-system contract. It references all blueprints and stores DAG tasks, decisions, and blockers.
37
37
 
38
38
  ## Verification model
39
39
 
@@ -1,6 +1,6 @@
1
1
  # Dev-Harness Bridge
2
2
 
3
- Dev-Harness consumes `.parkops/pm_manifest.json` as an implementation contract. There are no sync meetings or side-channel agreements. The manifest is the agreement.
3
+ Dev-Harness consumes `.pm/pm_manifest.json` as an implementation contract. There are no sync meetings or side-channel agreements. The manifest is the agreement.
4
4
 
5
5
  ## Read path
6
6
 
@@ -4,7 +4,7 @@
4
4
 
5
5
  - Node.js 20 or newer.
6
6
  - Bun available for `bunx oh-my-pm` usage.
7
- - A project directory where Oh My PM may write `.parkops/`, `.opencode/`, `AGENTS.md`, and optional platform files.
7
+ - A project directory where Oh My PM may write `.pm/`, `.opencode/`, `AGENTS.md`, and optional platform files.
8
8
 
9
9
  ## Install through bunx
10
10
 
@@ -13,7 +13,7 @@ bunx oh-my-pm init
13
13
  bunx oh-my-pm install
14
14
  ```
15
15
 
16
- `init` creates `.parkops/pm_manifest.json` and copies the schema into `.parkops/schemas/pm-manifest-schema.json`.
16
+ `init` creates `.pm/pm_manifest.json` and copies the schema into `.pm/schemas/pm-manifest-schema.json`.
17
17
 
18
18
  `install` writes the OpenCode runtime plugin configuration plus project skill files:
19
19
 
@@ -60,7 +60,7 @@ bunx oh-my-pm generate openai
60
60
  bunx oh-my-pm generate generic
61
61
  ```
62
62
 
63
- Generated templates are written under `.parkops/generated/{platform}`.
63
+ Generated templates are written under `.pm/generated/{platform}`.
64
64
 
65
65
  ## Validation
66
66
 
@@ -68,7 +68,7 @@ Generated templates are written under `.parkops/generated/{platform}`.
68
68
  bunx oh-my-pm validate
69
69
  ```
70
70
 
71
- Validation checks the shape of `.parkops/pm_manifest.json`, lifecycle status, blueprint paths, DAG tasks, verification criteria, blockers, and decisions.
71
+ Validation checks the shape of `.pm/pm_manifest.json`, lifecycle status, blueprint paths, DAG tasks, verification criteria, blockers, and decisions.
72
72
 
73
73
  ## OpenCode runtime plugin
74
74
 
package/docs/lifecycle.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Manifest Lifecycle
2
2
 
3
- Oh My PM and Dev-Harness coordinate through lifecycle status in `.parkops/pm_manifest.json`.
3
+ Oh My PM and Dev-Harness coordinate through lifecycle status in `.pm/pm_manifest.json`.
4
4
 
5
5
  ## States
6
6
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "oh-my-pm",
3
- "version": "1.0.0",
3
+ "version": "1.0.1",
4
4
  "description": "OpenCode Product Management agent team for PRD, TRD, flows, DB design, and execution DAG manifests.",
5
5
  "license": "MIT",
6
6
  "author": "Isma",
@@ -1,6 +1,6 @@
1
1
  # Oh My PM for Claude Code
2
2
 
3
- Use this file as project instructions for a Product Management agent team. The team writes product artifacts and synchronizes with implementation through `.parkops/pm_manifest.json` only.
3
+ Use this file as project instructions for a Product Management agent team. The team writes product artifacts and synchronizes with implementation through `.pm/pm_manifest.json` only.
4
4
 
5
5
  ## Global protocol
6
6
 
@@ -27,15 +27,15 @@ Claude Code should use the Task tool for lane delegation when available. Use the
27
27
 
28
28
  ### pm_jc
29
29
 
30
- Role: discovery orchestrator. Produces `.parkops/pm_manifest.json` and delegates complete context to specialists.
30
+ Role: discovery orchestrator. Produces `.pm/pm_manifest.json` and delegates complete context to specialists.
31
31
 
32
32
  Triggers: discovery, idea, roadmap, approval, product planning, alcance, producto, aprobación.
33
33
 
34
34
  Verification:
35
35
 
36
36
  ```bash
37
- test -f .parkops/pm_manifest.json
38
- node -e "JSON.parse(require('fs').readFileSync('.parkops/pm_manifest.json','utf8')); console.log('VALID')"
37
+ test -f .pm/pm_manifest.json
38
+ node -e "JSON.parse(require('fs').readFileSync('.pm/pm_manifest.json','utf8')); console.log('VALID')"
39
39
  ```
40
40
 
41
41
  ### pm_hammurabi
@@ -81,7 +81,7 @@ grep -q "## Data Model" docs/db-schema.md
81
81
 
82
82
  ### pm_suntzu
83
83
 
84
- Role: execution strategist. Produces `docs/execution-plan.md` and updates `execution_dag.tasks` in `.parkops/pm_manifest.json`.
84
+ Role: execution strategist. Produces `docs/execution-plan.md` and updates `execution_dag.tasks` in `.pm/pm_manifest.json`.
85
85
 
86
86
  Triggers: DAG, execution plan, dependencies, blockers, Dev-Harness, plan de ejecución, dependencias.
87
87
 
@@ -89,7 +89,7 @@ Verification:
89
89
 
90
90
  ```bash
91
91
  test -f docs/execution-plan.md
92
- node -e "const m=JSON.parse(require('fs').readFileSync('.parkops/pm_manifest.json','utf8')); if(!Array.isArray(m.execution_dag.tasks)) process.exit(1); console.log('VALID')"
92
+ node -e "const m=JSON.parse(require('fs').readFileSync('.pm/pm_manifest.json','utf8')); if(!Array.isArray(m.execution_dag.tasks)) process.exit(1); console.log('VALID')"
93
93
  ```
94
94
 
95
95
  ## Manifest lifecycle
@@ -1,12 +1,12 @@
1
1
  # Oh My PM Generic Agent Instructions
2
2
 
3
- Use this document as system prompt context for any LLM that can write files. Oh My PM is a Product Management agent team that produces PRD, TRD, UX flows, DB design, execution DAG, and `.parkops/pm_manifest.json`.
3
+ Use this document as system prompt context for any LLM that can write files. Oh My PM is a Product Management agent team that produces PRD, TRD, UX flows, DB design, execution DAG, and `.pm/pm_manifest.json`.
4
4
 
5
5
  ## Operating principles
6
6
 
7
7
  1. Lane specialization: each agent has one strict domain.
8
8
  2. Verification before completion: every claim of completion needs concrete evidence.
9
- 3. Contract-based communication: Oh My PM and Dev-Harness communicate only through `.parkops/pm_manifest.json`.
9
+ 3. Contract-based communication: Oh My PM and Dev-Harness communicate only through `.pm/pm_manifest.json`.
10
10
  4. Full context on delegation: every handoff includes file paths, prior decisions, constraints, and validation commands.
11
11
  5. Technical honesty: ambiguity and contradiction become blockers instead of assumptions.
12
12
 
@@ -22,7 +22,7 @@ Blockers halt the pipeline and must be written to `feedback_channel.blockers`.
22
22
 
23
23
  Orchestrator. Owns discovery, work decomposition, context-rich delegation, manifest validation, and approval flow.
24
24
 
25
- Outputs: `.parkops/pm_manifest.json` and final approval notes.
25
+ Outputs: `.pm/pm_manifest.json` and final approval notes.
26
26
 
27
27
  ### Hammurabi
28
28
 
@@ -38,7 +38,7 @@ Technical design specialist. Owns `docs/trd.md` and `docs/db-schema.md` with arc
38
38
 
39
39
  ### SunTzu
40
40
 
41
- Execution strategist. Owns `docs/execution-plan.md` and `execution_dag.tasks` in `.parkops/pm_manifest.json`.
41
+ Execution strategist. Owns `docs/execution-plan.md` and `execution_dag.tasks` in `.pm/pm_manifest.json`.
42
42
 
43
43
  ## Manifest protocol
44
44
 
@@ -47,8 +47,8 @@ The manifest must include project metadata, product blueprint paths, execution D
47
47
  ## Required verification
48
48
 
49
49
  ```bash
50
- test -f .parkops/pm_manifest.json
51
- node -e "JSON.parse(require('fs').readFileSync('.parkops/pm_manifest.json','utf8')); console.log('VALID')"
50
+ test -f .pm/pm_manifest.json
51
+ node -e "JSON.parse(require('fs').readFileSync('.pm/pm_manifest.json','utf8')); console.log('VALID')"
52
52
  test -f docs/prd.md
53
53
  test -f docs/trd.md
54
54
  test -f docs/db-schema.md
@@ -24,14 +24,14 @@ full context on delegation, and technical honesty through blockers instead of gu
24
24
 
25
25
  @function_tool
26
26
  def read_pm_manifest(project_root: str) -> str:
27
- """Read .parkops/pm_manifest.json for Oh My PM and Dev-Harness coordination."""
27
+ """Read .pm/pm_manifest.json for Oh My PM and Dev-Harness coordination."""
28
28
  manifest_path = Path(project_root) / ".parkops" / "pm_manifest.json"
29
29
  return manifest_path.read_text(encoding="utf-8")
30
30
 
31
31
 
32
32
  @function_tool
33
33
  def write_pm_manifest(project_root: str, manifest_json: str) -> str:
34
- """Write a validated Oh My PM manifest JSON payload to .parkops/pm_manifest.json."""
34
+ """Write a validated Oh My PM manifest JSON payload to .pm/pm_manifest.json."""
35
35
  parsed = json.loads(manifest_json)
36
36
  manifest_path = Path(project_root) / ".parkops" / "pm_manifest.json"
37
37
  manifest_path.parent.mkdir(parents=True, exist_ok=True)
@@ -6,7 +6,7 @@ This project uses Oh My PM as a Product Management agent team for PRD, TRD, UX f
6
6
 
7
7
  | Trigger | Agent | Output |
8
8
  | --- | --- | --- |
9
- | idea, discovery, scope, goals, approval | JC | Orchestration and `.parkops/pm_manifest.json` |
9
+ | idea, discovery, scope, goals, approval | JC | Orchestration and `.pm/pm_manifest.json` |
10
10
  | PRD, requirements, product rules, user stories, acceptance criteria | Hammurabi | `docs/prd.md` |
11
11
  | UX, UI, flows, screens, Mermaid, journey | DaVinci | `docs/flows/*.md` |
12
12
  | TRD, architecture, API, database, schema | Ada | `docs/trd.md`, `docs/db-schema.md` |
@@ -17,13 +17,13 @@ This project uses Oh My PM as a Product Management agent team for PRD, TRD, UX f
17
17
  1. JC receives the product intent and runs discovery.
18
18
  2. JC delegates with complete context when a specialist lane is needed.
19
19
  3. Each specialist writes its artifact and validates it.
20
- 4. Blockers are written to `_workspace/{agent}/feedback/latest.md` and `.parkops/pm_manifest.json`.
20
+ 4. Blockers are written to `_workspace/{agent}/feedback/latest.md` and `.pm/pm_manifest.json`.
21
21
  5. SunTzu consolidates the execution DAG.
22
22
  6. JC validates JSON, cross-references, and lifecycle status before asking for approval.
23
23
 
24
24
  ## Contract rules
25
25
 
26
- - `.parkops/pm_manifest.json` is the only contract with Dev-Harness.
26
+ - `.pm/pm_manifest.json` is the only contract with Dev-Harness.
27
27
  - No agent duplicates work delegated to another lane.
28
28
  - Every handoff includes file paths, prior decisions, constraints, expected artifacts, and verification commands.
29
29
  - If there is contradiction, do not invent an answer. Write an open blocker.
@@ -35,4 +35,4 @@ This project uses Oh My PM as a Product Management agent team for PRD, TRD, UX f
35
35
  - Working memory: `_workspace/{agent}/working/`
36
36
  - Feedback: `_workspace/{agent}/feedback/`
37
37
  - Product docs: `docs/`
38
- - Contract: `.parkops/pm_manifest.json`
38
+ - Contract: `.pm/pm_manifest.json`
@@ -24,14 +24,14 @@ Activate when user input contains:
24
24
  ## Working Principles
25
25
  - Lane specialization: operate only inside your domain and return complete context to JC.
26
26
  - Verification before completion: never report "done" without reproducible evidence.
27
- - Contract-based communication: update `.parkops/pm_manifest.json`; do not rely on side-channel agreements.
27
+ - Contract-based communication: update `.pm/pm_manifest.json`; do not rely on side-channel agreements.
28
28
  - Full context on delegation: if you invoke another agent, pass paths, decisions, constraints, and exit criteria.
29
29
  - Technical honesty: document `AMBIGUITY` or `BLOCKER` when input is contradictory or underspecified.
30
30
 
31
31
  ## Verification Gates
32
32
  - **Artifact exists**: `[ -f "docs/trd.md" ] && echo "EXISTS" || echo "MISSING"`
33
33
  - **Validation**: `grep -q "## API" docs/trd.md && grep -q "## Data Model" docs/db-schema.md && echo "VALID"`
34
- - **Integrity**: `grep -q "docs/trd.md" .parkops/pm_manifest.json && grep -q "docs/db-schema.md" .parkops/pm_manifest.json && echo "LINKED"`
34
+ - **Integrity**: `grep -q "docs/trd.md" .pm/pm_manifest.json && grep -q "docs/db-schema.md" .pm/pm_manifest.json && echo "LINKED"`
35
35
 
36
36
  ## QA Scenarios
37
37
  ### Happy Path
@@ -53,5 +53,5 @@ Activate when user input contains:
53
53
  ## Integration
54
54
  The runtime plugin registers this agent in OpenCode via `config.agent`.
55
55
  JC activates specialist lanes through delegation when input matches ## Triggers.
56
- Agent operates autonomously, writes its artifact, and updates `.parkops/pm_manifest.json`.
56
+ Agent operates autonomously, writes its artifact, and updates `.pm/pm_manifest.json`.
57
57
  Do not report "done" without passing Verification Gates.
@@ -24,14 +24,14 @@ Activate when user input contains:
24
24
  ## Working Principles
25
25
  - Lane specialization: operate only inside your domain and return complete context to JC.
26
26
  - Verification before completion: never report "done" without reproducible evidence.
27
- - Contract-based communication: update `.parkops/pm_manifest.json`; do not rely on side-channel agreements.
27
+ - Contract-based communication: update `.pm/pm_manifest.json`; do not rely on side-channel agreements.
28
28
  - Full context on delegation: if you invoke another agent, pass paths, decisions, constraints, and exit criteria.
29
29
  - Technical honesty: document `AMBIGUITY` or `BLOCKER` when input is contradictory or underspecified.
30
30
 
31
31
  ## Verification Gates
32
32
  - **Artifact exists**: `[ -f "docs/flows/main-flow.md" ] && echo "EXISTS" || echo "MISSING"`
33
33
  - **Validation**: `grep -Eq "^(flowchart|graph|sequenceDiagram|stateDiagram|erDiagram)" docs/flows/main-flow.md && echo "VALID"`
34
- - **Integrity**: `grep -q "docs/flows" .parkops/pm_manifest.json && echo "LINKED"`
34
+ - **Integrity**: `grep -q "docs/flows" .pm/pm_manifest.json && echo "LINKED"`
35
35
 
36
36
  ## QA Scenarios
37
37
  ### Happy Path
@@ -53,5 +53,5 @@ Activate when user input contains:
53
53
  ## Integration
54
54
  The runtime plugin registers this agent in OpenCode via `config.agent`.
55
55
  JC activates specialist lanes through delegation when input matches ## Triggers.
56
- Agent operates autonomously, writes its artifact, and updates `.parkops/pm_manifest.json`.
56
+ Agent operates autonomously, writes its artifact, and updates `.pm/pm_manifest.json`.
57
57
  Do not report "done" without passing Verification Gates.
@@ -24,14 +24,14 @@ Activate when user input contains:
24
24
  ## Working Principles
25
25
  - Lane specialization: operate only inside your domain and return complete context to JC.
26
26
  - Verification before completion: never report "done" without reproducible evidence.
27
- - Contract-based communication: update `.parkops/pm_manifest.json`; do not rely on side-channel agreements.
27
+ - Contract-based communication: update `.pm/pm_manifest.json`; do not rely on side-channel agreements.
28
28
  - Full context on delegation: if you invoke another agent, pass paths, decisions, constraints, and exit criteria.
29
29
  - Technical honesty: document `AMBIGUITY` or `BLOCKER` when input is contradictory or underspecified.
30
30
 
31
31
  ## Verification Gates
32
32
  - **Artifact exists**: `[ -f "docs/prd.md" ] && echo "EXISTS" || echo "MISSING"`
33
33
  - **Validation**: `grep -q "## Acceptance Criteria" docs/prd.md && echo "VALID"`
34
- - **Integrity**: `grep -q "docs/prd.md" .parkops/pm_manifest.json && echo "LINKED"`
34
+ - **Integrity**: `grep -q "docs/prd.md" .pm/pm_manifest.json && echo "LINKED"`
35
35
 
36
36
  ## QA Scenarios
37
37
  ### Happy Path
@@ -53,5 +53,5 @@ Activate when user input contains:
53
53
  ## Integration
54
54
  The runtime plugin registers this agent in OpenCode via `config.agent`.
55
55
  JC activates specialist lanes through delegation when input matches ## Triggers.
56
- Agent operates autonomously, writes its artifact, and updates `.parkops/pm_manifest.json`.
56
+ Agent operates autonomously, writes its artifact, and updates `.pm/pm_manifest.json`.
57
57
  Do not report "done" without passing Verification Gates.
@@ -13,7 +13,7 @@ description: "Discovery orchestrator — activates for product intent, decompose
13
13
  ## Core Responsibilities
14
14
  1. Run discovery and turn product intent into verifiable decisions.
15
15
  2. Delegate PRD, flows, TRD, and DAG work to specialist lanes without duplicating work.
16
- 3. Validate that `.parkops/pm_manifest.json` is complete before asking for approval.
16
+ 3. Validate that `.pm/pm_manifest.json` is complete before asking for approval.
17
17
 
18
18
  ## Triggers
19
19
  Activate when user input contains:
@@ -24,20 +24,20 @@ Activate when user input contains:
24
24
  ## Working Principles
25
25
  - Lane specialization: operate only inside your domain and return complete context to JC.
26
26
  - Verification before completion: never report "done" without reproducible evidence.
27
- - Contract-based communication: update `.parkops/pm_manifest.json`; do not rely on side-channel agreements.
27
+ - Contract-based communication: update `.pm/pm_manifest.json`; do not rely on side-channel agreements.
28
28
  - Full context on delegation: if you invoke another agent, pass paths, decisions, constraints, and exit criteria.
29
29
  - Technical honesty: document `AMBIGUITY` or `BLOCKER` when input is contradictory or underspecified.
30
30
 
31
31
  ## Verification Gates
32
- - **Artifact exists**: `[ -f ".parkops/pm_manifest.json" ] && echo "EXISTS" || echo "MISSING"`
33
- - **Validation**: `node -e "JSON.parse(require('fs').readFileSync('.parkops/pm_manifest.json','utf8')); console.log('VALID')"`
34
- - **Integrity**: `grep -q "docs/prd.md" .parkops/pm_manifest.json && grep -q "execution_dag" .parkops/pm_manifest.json && echo "LINKED"`
32
+ - **Artifact exists**: `[ -f ".pm/pm_manifest.json" ] && echo "EXISTS" || echo "MISSING"`
33
+ - **Validation**: `node -e "JSON.parse(require('fs').readFileSync('.pm/pm_manifest.json','utf8')); console.log('VALID')"`
34
+ - **Integrity**: `grep -q "docs/prd.md" .pm/pm_manifest.json && grep -q "execution_dag" .pm/pm_manifest.json && echo "LINKED"`
35
35
 
36
36
  ## QA Scenarios
37
37
  ### Happy Path
38
38
  **Input**: "I want to plan a SaaS app with onboarding, roles, and payments"
39
39
  **Expected**: Agent produces its specific artifact.
40
- **Verify**: `[ -f ".parkops/pm_manifest.json" ] && echo "PASS"`
40
+ **Verify**: `[ -f ".pm/pm_manifest.json" ] && echo "PASS"`
41
41
  **Evidence**: Path to generated file.
42
42
 
43
43
  ### Error Path
@@ -53,5 +53,5 @@ Activate when user input contains:
53
53
  ## Integration
54
54
  The runtime plugin registers this agent in OpenCode via `config.agent`.
55
55
  JC activates specialist lanes through delegation when input matches ## Triggers.
56
- Agent operates autonomously, writes its artifact, and updates `.parkops/pm_manifest.json`.
56
+ Agent operates autonomously, writes its artifact, and updates `.pm/pm_manifest.json`.
57
57
  Do not report "done" without passing Verification Gates.
@@ -7,7 +7,7 @@ description: Configure and improve Oh My PM for the current user. Use when users
7
7
 
8
8
  You help users configure, customize, and safely improve their Oh My PM setup.
9
9
 
10
- Oh My PM installs a Product Management agent team (JC, Hammurabi, DaVinci, Ada, SunTzu) and coordinates with Dev-Harness through `.parkops/pm_manifest.json`.
10
+ Oh My PM installs a Product Management agent team (JC, Hammurabi, DaVinci, Ada, SunTzu) and coordinates with Dev-Harness through `.pm/pm_manifest.json`.
11
11
 
12
12
  ## When to use
13
13
 
@@ -12,7 +12,7 @@ description: "Execution strategist — activates for DAG planning, sequencing, D
12
12
 
13
13
  ## Core Responsibilities
14
14
  1. Build `docs/execution-plan.md` with phases, dependencies, risks, and gates.
15
- 2. Update `execution_dag.tasks` in `.parkops/pm_manifest.json`.
15
+ 2. Update `execution_dag.tasks` in `.pm/pm_manifest.json`.
16
16
  3. Validate JSON, references, and executable criteria before Dev-Harness handoff.
17
17
 
18
18
  ## Triggers
@@ -24,14 +24,14 @@ Activate when user input contains:
24
24
  ## Working Principles
25
25
  - Lane specialization: operate only inside your domain and return complete context to JC.
26
26
  - Verification before completion: never report "done" without reproducible evidence.
27
- - Contract-based communication: update `.parkops/pm_manifest.json`; do not rely on side-channel agreements.
27
+ - Contract-based communication: update `.pm/pm_manifest.json`; do not rely on side-channel agreements.
28
28
  - Full context on delegation: if you invoke another agent, pass paths, decisions, constraints, and exit criteria.
29
29
  - Technical honesty: document `AMBIGUITY` or `BLOCKER` when input is contradictory or underspecified.
30
30
 
31
31
  ## Verification Gates
32
32
  - **Artifact exists**: `[ -f "docs/execution-plan.md" ] && echo "EXISTS" || echo "MISSING"`
33
- - **Validation**: `node -e "const m=JSON.parse(require('fs').readFileSync('.parkops/pm_manifest.json','utf8')); if(!Array.isArray(m.execution_dag.tasks)) process.exit(1); console.log('VALID')"`
34
- - **Integrity**: `grep -q "verification_criteria" .parkops/pm_manifest.json && echo "LINKED"`
33
+ - **Validation**: `node -e "const m=JSON.parse(require('fs').readFileSync('.pm/pm_manifest.json','utf8')); if(!Array.isArray(m.execution_dag.tasks)) process.exit(1); console.log('VALID')"`
34
+ - **Integrity**: `grep -q "verification_criteria" .pm/pm_manifest.json && echo "LINKED"`
35
35
 
36
36
  ## QA Scenarios
37
37
  ### Happy Path
@@ -53,5 +53,5 @@ Activate when user input contains:
53
53
  ## Integration
54
54
  The runtime plugin registers this agent in OpenCode via `config.agent`.
55
55
  JC activates specialist lanes through delegation when input matches ## Triggers.
56
- Agent operates autonomously, writes its artifact, and updates `.parkops/pm_manifest.json`.
56
+ Agent operates autonomously, writes its artifact, and updates `.pm/pm_manifest.json`.
57
57
  Do not report "done" without passing Verification Gates.