@intentsolutionsio/plane 0.1.1 → 0.1.2
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@intentsolutionsio/plane",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.2",
|
|
4
4
|
"description": "Plane is a team behavior observatory — synthesize Plane API data into observations about how teams actually behave under pressure (cycle velocity vs. plan, ownership churn, reviewer gate strength, pri",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"plane",
|
|
@@ -7,6 +7,7 @@ Each command answers a question that **cannot** be answered from any single Plan
|
|
|
7
7
|
**Question**: Does this team's cycle velocity match its planning?
|
|
8
8
|
|
|
9
9
|
**Synthesizes**:
|
|
10
|
+
|
|
10
11
|
- `list_cycles` → enumerate completed cycles
|
|
11
12
|
- `get_cycle` (per cycle) → planned start/end + actual completion counts
|
|
12
13
|
- `list_cycle_issues` (per cycle) → estimate_point sum vs. completed_issues sum
|
|
@@ -38,6 +39,7 @@ scope per cycle or extend cycle length.
|
|
|
38
39
|
**Question**: Which tickets are quietly failing under shared ownership?
|
|
39
40
|
|
|
40
41
|
**Synthesizes**:
|
|
42
|
+
|
|
41
43
|
- `list_project_issues` → open issues
|
|
42
44
|
- `list_states` → identify "In Progress" state UUIDs
|
|
43
45
|
- `get_issue_comments` (per stale candidate) → assignee changes during the open window
|
|
@@ -67,6 +69,7 @@ Behavioral signal: BRAVES-78 has 3 assignees and hasn't moved in 11 days
|
|
|
67
69
|
**Question**: Which reviewers gate-keep harder than the spec demands?
|
|
68
70
|
|
|
69
71
|
**Synthesizes**:
|
|
72
|
+
|
|
70
73
|
- `list_project_issues` filtered to recently-closed
|
|
71
74
|
- `get_issue_comments` (per closed issue) → look for "blocked by reviewer" pattern + reviewer assignment timing
|
|
72
75
|
|
|
@@ -96,6 +99,7 @@ queue.
|
|
|
96
99
|
**Question**: Does the team plan high-priority work but ship low-priority work?
|
|
97
100
|
|
|
98
101
|
**Synthesizes**:
|
|
102
|
+
|
|
99
103
|
- `list_cycles` → recent closed cycles
|
|
100
104
|
- `list_cycle_issues` (per cycle) → priority distribution at planning time
|
|
101
105
|
- Cross-reference with `get_issue_using_readable_identifier` for issues marked `completed` in the cycle
|
|
@@ -129,6 +133,7 @@ opportunistically, or planning is happening at the wrong time/place.
|
|
|
129
133
|
**Question**: Which engineers are spread across too many active projects?
|
|
130
134
|
|
|
131
135
|
**Synthesizes**:
|
|
136
|
+
|
|
132
137
|
- `get_workspace_members` → engineer roster
|
|
133
138
|
- `list_project_issues` (across all active projects, filtered to assignee × open state)
|
|
134
139
|
- `list_modules` (used as a project-internal grouping signal)
|