enterprise-delivery 0.1.0
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/.claude-plugin/plugin.json +21 -0
- package/.codex-plugin/plugin.json +36 -0
- package/AGENTS.md +73 -0
- package/README.md +127 -0
- package/package.json +28 -0
- package/scripts/enterprise-delivery-validate.mjs +11 -0
- package/skills/add-requirement/SKILL.md +52 -0
- package/skills/analyze-requirement/SKILL.md +48 -0
- package/skills/analyze-tech-stack/SKILL.md +36 -0
- package/skills/change-requirement/SKILL.md +37 -0
- package/skills/complete-task/SKILL.md +46 -0
- package/skills/delivery-lead/SKILL.md +221 -0
- package/skills/delivery-planning/SKILL.md +27 -0
- package/skills/enterprise-kickoff/SKILL.md +25 -0
- package/skills/feature-gate/SKILL.md +22 -0
- package/skills/release-gate/SKILL.md +24 -0
- package/skills/sprint-gate/SKILL.md +23 -0
- package/skills/start-task/SKILL.md +39 -0
- package/skills/story-intake/SKILL.md +23 -0
- package/skills/update-coding-rules/SKILL.md +32 -0
- package/src/cli.mjs +220 -0
- package/src/frontmatter.mjs +121 -0
- package/src/init.mjs +54 -0
- package/src/install-codex.mjs +121 -0
- package/src/markdown.mjs +58 -0
- package/src/repository.mjs +59 -0
- package/src/rules.mjs +814 -0
- package/templates/docs/enterprise/architecture-overview.md +17 -0
- package/templates/docs/enterprise/change-log.md +4 -0
- package/templates/docs/enterprise/changes/CHG-0000-template.md +37 -0
- package/templates/docs/enterprise/current-state.md +48 -0
- package/templates/docs/enterprise/decision-log.md +5 -0
- package/templates/docs/enterprise/product-backlog.md +5 -0
- package/templates/docs/enterprise/project-charter.md +25 -0
- package/templates/docs/enterprise/project-vision.md +61 -0
- package/templates/docs/enterprise/releases/RELEASE-ID/release-notes.md +21 -0
- package/templates/docs/enterprise/releases/RELEASE-ID/release-plan.md +18 -0
- package/templates/docs/enterprise/releases/RELEASE-ID/traceability-matrix.md +5 -0
- package/templates/docs/enterprise/risk-register.md +5 -0
- package/templates/docs/enterprise/roadmap.md +13 -0
- package/templates/docs/enterprise/sprints/SPRINT-ID/sprint-plan.md +21 -0
- package/templates/docs/enterprise/sprints/SPRINT-ID/status-report.md +29 -0
- package/templates/docs/enterprise/stakeholder-register.md +6 -0
- package/templates/docs/enterprise/stories/STORY-0000-template.md +59 -0
- package/templates/docs/enterprise/task-graph.json +24 -0
- package/templates/docs/enterprise/test-strategy.md +15 -0
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
# Architecture Overview
|
|
2
|
+
|
|
3
|
+
## Confirmed Facts
|
|
4
|
+
|
|
5
|
+
- No architecture facts have been confirmed.
|
|
6
|
+
|
|
7
|
+
## Inferred Facts
|
|
8
|
+
|
|
9
|
+
- No architecture facts have been inferred.
|
|
10
|
+
|
|
11
|
+
## Unknowns
|
|
12
|
+
|
|
13
|
+
- System boundaries require human confirmation.
|
|
14
|
+
|
|
15
|
+
## Integration Points
|
|
16
|
+
|
|
17
|
+
- No integration points have been confirmed.
|
|
@@ -0,0 +1,37 @@
|
|
|
1
|
+
---
|
|
2
|
+
id: CHG-0000
|
|
3
|
+
title: Replace with change title
|
|
4
|
+
status: draft
|
|
5
|
+
related_stories:
|
|
6
|
+
- STORY-0000
|
|
7
|
+
external_links: []
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
# CHG-0000 Replace With Change Title
|
|
11
|
+
|
|
12
|
+
## Reason
|
|
13
|
+
|
|
14
|
+
Explain why this change is needed.
|
|
15
|
+
|
|
16
|
+
## Impact
|
|
17
|
+
|
|
18
|
+
Describe files, modules, commands, docs, or delivery artifacts affected by the change.
|
|
19
|
+
|
|
20
|
+
## Approval
|
|
21
|
+
|
|
22
|
+
Pending review by the relevant owner.
|
|
23
|
+
|
|
24
|
+
## Evidence
|
|
25
|
+
|
|
26
|
+
Planned:
|
|
27
|
+
|
|
28
|
+
- `npm test`
|
|
29
|
+
- `npm run gate:feature -- --story STORY-0000`
|
|
30
|
+
|
|
31
|
+
Actual:
|
|
32
|
+
|
|
33
|
+
- Not run yet.
|
|
34
|
+
|
|
35
|
+
## Rollout Notes
|
|
36
|
+
|
|
37
|
+
No special rollout steps identified.
|
|
@@ -0,0 +1,48 @@
|
|
|
1
|
+
# Current State
|
|
2
|
+
|
|
3
|
+
Last updated: unknown
|
|
4
|
+
|
|
5
|
+
## Active Stories
|
|
6
|
+
|
|
7
|
+
- Unknown until story intake is complete.
|
|
8
|
+
|
|
9
|
+
## Active Changes
|
|
10
|
+
|
|
11
|
+
- Unknown until change records are created.
|
|
12
|
+
|
|
13
|
+
## Failing Tests
|
|
14
|
+
|
|
15
|
+
- Unknown until verification is run.
|
|
16
|
+
|
|
17
|
+
## TODOs
|
|
18
|
+
|
|
19
|
+
- Unknown until discovered from code, stories, or human input.
|
|
20
|
+
|
|
21
|
+
## Coverage
|
|
22
|
+
|
|
23
|
+
- Unknown until measured.
|
|
24
|
+
|
|
25
|
+
## Unresolved Bugs
|
|
26
|
+
|
|
27
|
+
- Unknown until confirmed by tests, issues, logs, or human input.
|
|
28
|
+
|
|
29
|
+
## Recent Commits
|
|
30
|
+
|
|
31
|
+
- Unknown until inspected with `git log`.
|
|
32
|
+
|
|
33
|
+
## Active Risks
|
|
34
|
+
|
|
35
|
+
- See `docs/enterprise/risk-register.md`.
|
|
36
|
+
|
|
37
|
+
## Active Decisions
|
|
38
|
+
|
|
39
|
+
- See `docs/enterprise/decision-log.md`.
|
|
40
|
+
|
|
41
|
+
## Current Task Graph
|
|
42
|
+
|
|
43
|
+
- See `docs/enterprise/task-graph.json`.
|
|
44
|
+
|
|
45
|
+
## Next Verification Commands
|
|
46
|
+
|
|
47
|
+
- `npm test`
|
|
48
|
+
- `node scripts/enterprise-delivery-validate.mjs validate repo`
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
# Project Charter
|
|
2
|
+
|
|
3
|
+
## Purpose
|
|
4
|
+
|
|
5
|
+
Source confidence: unknown
|
|
6
|
+
|
|
7
|
+
Describe the business purpose this project serves.
|
|
8
|
+
|
|
9
|
+
## Target Users
|
|
10
|
+
|
|
11
|
+
Source confidence: unknown
|
|
12
|
+
|
|
13
|
+
- Unknown until confirmed by a human.
|
|
14
|
+
|
|
15
|
+
## Outcomes
|
|
16
|
+
|
|
17
|
+
Source confidence: unknown
|
|
18
|
+
|
|
19
|
+
- Unknown until confirmed by a human.
|
|
20
|
+
|
|
21
|
+
## Constraints
|
|
22
|
+
|
|
23
|
+
Source confidence: unknown
|
|
24
|
+
|
|
25
|
+
- Unknown until confirmed by a human.
|
|
@@ -0,0 +1,61 @@
|
|
|
1
|
+
# Project Vision
|
|
2
|
+
|
|
3
|
+
## Product Goals
|
|
4
|
+
|
|
5
|
+
Source confidence: unknown
|
|
6
|
+
|
|
7
|
+
- State the durable outcomes this project exists to create.
|
|
8
|
+
- Keep goals measurable enough that future stories can trace back to them.
|
|
9
|
+
|
|
10
|
+
## Non-Goals
|
|
11
|
+
|
|
12
|
+
Source confidence: unknown
|
|
13
|
+
|
|
14
|
+
- List attractive ideas this project explicitly should not pursue yet.
|
|
15
|
+
- Use this section to protect focus during AI-assisted implementation.
|
|
16
|
+
|
|
17
|
+
## Target Users
|
|
18
|
+
|
|
19
|
+
Source confidence: unknown
|
|
20
|
+
|
|
21
|
+
- Unknown until confirmed by a human.
|
|
22
|
+
|
|
23
|
+
## Spec Principles
|
|
24
|
+
|
|
25
|
+
- Requirements should be captured before implementation begins.
|
|
26
|
+
- Every delivery-impacting change should trace from requirement to story, change, evidence, and release or sprint state.
|
|
27
|
+
- Unknown facts should remain marked as `unknown` or `inferred`.
|
|
28
|
+
|
|
29
|
+
## Architecture Principles
|
|
30
|
+
|
|
31
|
+
- Prefer small modules with explicit responsibilities and reviewable interfaces.
|
|
32
|
+
- Keep durable domain decisions in `docs/enterprise/decision-log.md`.
|
|
33
|
+
- Keep delivery risks in `docs/enterprise/risk-register.md`.
|
|
34
|
+
- Avoid architecture that requires undocumented agent memory to operate safely.
|
|
35
|
+
|
|
36
|
+
## Forbidden Patterns
|
|
37
|
+
|
|
38
|
+
- Do not invent stakeholders, approvals, roadmap commitments, release readiness, or historical facts.
|
|
39
|
+
- Do not start implementation for delivery-impacting work without a linked `STORY-*` and `CHG-*`.
|
|
40
|
+
- Do not hide unresolved bugs, failing tests, or known risks outside the repository.
|
|
41
|
+
- Do not create parallel source-of-truth documents outside `docs/enterprise/`.
|
|
42
|
+
|
|
43
|
+
## Coding Philosophy
|
|
44
|
+
|
|
45
|
+
- Optimize for boring, inspectable changes over clever abstractions.
|
|
46
|
+
- Match the project's existing language, framework, and testing patterns.
|
|
47
|
+
- Add abstractions only when they remove real complexity or enforce a useful boundary.
|
|
48
|
+
- Prefer command evidence over claims of completion.
|
|
49
|
+
|
|
50
|
+
## Quality Bar
|
|
51
|
+
|
|
52
|
+
- Tests and validation gates should be known before implementation starts.
|
|
53
|
+
- A feature is not complete until relevant test evidence is recorded.
|
|
54
|
+
- Validator exit code `1` is a delivery blocker, not a tool failure.
|
|
55
|
+
|
|
56
|
+
## AI Collaboration Rules
|
|
57
|
+
|
|
58
|
+
- Read `docs/enterprise/project-vision.md`, `docs/enterprise/current-state.md`, and `docs/enterprise/task-graph.json` before planning substantial work.
|
|
59
|
+
- Update `current-state.md` when failing tests, unresolved bugs, active stories, or next verification commands change.
|
|
60
|
+
- Update `task-graph.json` when task dependencies, statuses, or evidence change.
|
|
61
|
+
- Ask for human confirmation before marking uncertain facts as confirmed.
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
# Release RELEASE-ID Notes
|
|
2
|
+
|
|
3
|
+
## Summary
|
|
4
|
+
|
|
5
|
+
Summarize the release outcome.
|
|
6
|
+
|
|
7
|
+
## Stories
|
|
8
|
+
|
|
9
|
+
- STORY-0000
|
|
10
|
+
|
|
11
|
+
## Changes
|
|
12
|
+
|
|
13
|
+
- CHG-0000
|
|
14
|
+
|
|
15
|
+
## Verification Evidence
|
|
16
|
+
|
|
17
|
+
- Not run yet.
|
|
18
|
+
|
|
19
|
+
## Known Issues
|
|
20
|
+
|
|
21
|
+
- None recorded.
|
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+
# Release RELEASE-ID Plan
|
|
2
|
+
|
|
3
|
+
## Scope
|
|
4
|
+
|
|
5
|
+
- STORY-0000
|
|
6
|
+
|
|
7
|
+
## Included Changes
|
|
8
|
+
|
|
9
|
+
- CHG-0000
|
|
10
|
+
|
|
11
|
+
## Verification Plan
|
|
12
|
+
|
|
13
|
+
- `npm test`
|
|
14
|
+
- `npm run gate:release -- --release RELEASE-ID`
|
|
15
|
+
|
|
16
|
+
## Risks And Blockers
|
|
17
|
+
|
|
18
|
+
- No known release blockers.
|
|
@@ -0,0 +1,5 @@
|
|
|
1
|
+
# Risk Register
|
|
2
|
+
|
|
3
|
+
| ID | Risk | Impact | Mitigation | Owner | Status |
|
|
4
|
+
| --- | --- | --- | --- | --- | --- |
|
|
5
|
+
| RISK-0001 | Delivery governance facts are incomplete after onboarding | Medium | Mark unknowns explicitly and request human confirmation | Unknown | open |
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
# Sprint SPRINT-ID Plan
|
|
2
|
+
|
|
3
|
+
## Goal
|
|
4
|
+
|
|
5
|
+
State the sprint outcome in one or two sentences.
|
|
6
|
+
|
|
7
|
+
## Committed Stories
|
|
8
|
+
|
|
9
|
+
- STORY-0000
|
|
10
|
+
|
|
11
|
+
## Capacity And Constraints
|
|
12
|
+
|
|
13
|
+
- Capacity has not been confirmed.
|
|
14
|
+
|
|
15
|
+
## Risks
|
|
16
|
+
|
|
17
|
+
- No new risks identified.
|
|
18
|
+
|
|
19
|
+
## Decisions
|
|
20
|
+
|
|
21
|
+
- No new decisions identified.
|
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
# Sprint SPRINT-ID Status Report
|
|
2
|
+
|
|
3
|
+
## Summary
|
|
4
|
+
|
|
5
|
+
State current sprint status.
|
|
6
|
+
|
|
7
|
+
## Completed Stories
|
|
8
|
+
|
|
9
|
+
- None yet.
|
|
10
|
+
|
|
11
|
+
## Carry Over
|
|
12
|
+
|
|
13
|
+
- None yet.
|
|
14
|
+
|
|
15
|
+
## Blockers
|
|
16
|
+
|
|
17
|
+
- None.
|
|
18
|
+
|
|
19
|
+
## Risks
|
|
20
|
+
|
|
21
|
+
No new risks.
|
|
22
|
+
|
|
23
|
+
## Decisions
|
|
24
|
+
|
|
25
|
+
No new decisions.
|
|
26
|
+
|
|
27
|
+
## Evidence
|
|
28
|
+
|
|
29
|
+
- Not run yet.
|
|
@@ -0,0 +1,59 @@
|
|
|
1
|
+
---
|
|
2
|
+
id: STORY-0000
|
|
3
|
+
title: Replace with story title
|
|
4
|
+
status: draft
|
|
5
|
+
priority: medium
|
|
6
|
+
linked_changes:
|
|
7
|
+
- CHG-0000
|
|
8
|
+
external_links: []
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
# STORY-0000 Replace With Story Title
|
|
12
|
+
|
|
13
|
+
## Requirement
|
|
14
|
+
|
|
15
|
+
Source: Replace with human request, issue link, customer request, or product decision.
|
|
16
|
+
|
|
17
|
+
## Business Value
|
|
18
|
+
|
|
19
|
+
Explain the outcome this story supports.
|
|
20
|
+
|
|
21
|
+
## Acceptance Criteria
|
|
22
|
+
|
|
23
|
+
- The expected behavior is explicit and reviewable.
|
|
24
|
+
- The validation evidence needed for completion is known before implementation starts.
|
|
25
|
+
|
|
26
|
+
## Non-Functional Criteria
|
|
27
|
+
|
|
28
|
+
- No new performance, security, accessibility, or reliability requirements have been identified.
|
|
29
|
+
|
|
30
|
+
## Dependencies
|
|
31
|
+
|
|
32
|
+
- No known dependencies.
|
|
33
|
+
|
|
34
|
+
## Risk Impact
|
|
35
|
+
|
|
36
|
+
- No new risks identified.
|
|
37
|
+
|
|
38
|
+
## Docs Impact
|
|
39
|
+
|
|
40
|
+
No impact: replace this with a reason, or describe the documentation updates.
|
|
41
|
+
|
|
42
|
+
## Test Evidence
|
|
43
|
+
|
|
44
|
+
Planned:
|
|
45
|
+
|
|
46
|
+
- `npm test`
|
|
47
|
+
- `npm run gate:feature -- --story STORY-0000`
|
|
48
|
+
|
|
49
|
+
Actual:
|
|
50
|
+
|
|
51
|
+
- Not run yet.
|
|
52
|
+
|
|
53
|
+
## Implementation Links
|
|
54
|
+
|
|
55
|
+
- Pending implementation reference.
|
|
56
|
+
|
|
57
|
+
## Change History
|
|
58
|
+
|
|
59
|
+
- Draft story created.
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schema_version": 1,
|
|
3
|
+
"updated_at": "unknown",
|
|
4
|
+
"tasks": {
|
|
5
|
+
"task_1": {
|
|
6
|
+
"title": "Replace with task title",
|
|
7
|
+
"status": "planned",
|
|
8
|
+
"depends_on": [],
|
|
9
|
+
"story_id": "STORY-0000",
|
|
10
|
+
"change_id": "CHG-0000",
|
|
11
|
+
"evidence": [],
|
|
12
|
+
"notes": "Describe what this task delivers and any constraints the agent must preserve."
|
|
13
|
+
},
|
|
14
|
+
"task_2": {
|
|
15
|
+
"title": "Replace with dependent task title",
|
|
16
|
+
"status": "planned",
|
|
17
|
+
"depends_on": ["task_1"],
|
|
18
|
+
"story_id": "STORY-0000",
|
|
19
|
+
"change_id": "CHG-0000",
|
|
20
|
+
"evidence": [],
|
|
21
|
+
"notes": "Use depends_on to make sequencing explicit for humans and AI agents."
|
|
22
|
+
}
|
|
23
|
+
}
|
|
24
|
+
}
|
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
# Test Strategy
|
|
2
|
+
|
|
3
|
+
## Required Evidence
|
|
4
|
+
|
|
5
|
+
- Feature work must include command-based test evidence or an explicit not-applicable reason.
|
|
6
|
+
|
|
7
|
+
## Test Levels
|
|
8
|
+
|
|
9
|
+
- Unit: required when business logic is changed.
|
|
10
|
+
- Integration: required when module boundaries or external interfaces change.
|
|
11
|
+
- Manual: allowed only when automated verification is not practical and the reason is recorded.
|
|
12
|
+
|
|
13
|
+
## Verification Commands
|
|
14
|
+
|
|
15
|
+
- No project-specific verification commands have been confirmed.
|