opencode-sdlc-plugin 0.3.2 → 1.1.0

package/commands/sdlc-design.md

@@ -1,246 +0,0 @@
----
-description: Event Modeling design workflow - discover domains, design workflows, generate scenarios
----
-
-# SDLC Design - Event Modeling
-
-## Instructions
-
-You receive: `$ARGUMENTS`
-
-Parse the argument to determine the design action:
-
-| Command | Action |
-|---------|--------|
-| `discover <domain>` | Domain discovery for a new domain |
-| `workflow <name>` | Design a workflow using 9-step methodology |
-| `gwt <workflow>` | Generate GWT scenarios for a workflow |
-| `validate [scope]` | Validate event model completeness |
-| (no args) | Show status and next recommended action |
-
----
-
-## Git Operations Policy
-
-**AUTOMATIC GIT OPERATIONS ARE PROHIBITED**
-
-You must NOT perform any git operations automatically:
-- Do NOT run `git commit` to save changes
-- Do NOT run `git push` to push to remote
-- Do NOT run `gh pr create` or other GitHub CLI operations
-
-**Git operations are ONLY permitted if the user explicitly requests them.**
-
----
-
-## Action: `discover <domain>`
-
-Run domain discovery to identify actors, goals, processes, and boundaries.
-
-```
-sdlc_discover_domain({
-  domainName: "<domain name from argument>",
-  context: "<any additional context from the conversation>"
-})
-```
-
-**Example:** `/sdlc:design discover Order Management`
-
-After discovery:
-1. Review the generated `docs/event_model/domain/overview.md`
-2. Suggest next steps: "Run `/sdlc:design workflow <name>` to design specific workflows"
-
----
-
-## Action: `workflow <name>`
-
-Design a workflow using the 9-step Event Modeling methodology.
-
-```
-sdlc_design_workflow({
-  workflowName: "<workflow name from argument>"
-})
-```
-
-**Example:** `/sdlc:design workflow Order Submission`
-
-The tool will:
-1. Load domain context if available
-2. Guide through the 9 steps (events, timeline, UIs, commands, rules, details, read models, automations, slices)
-3. Create `docs/event_model/workflows/<name>/overview.md`
-
-After workflow design:
-1. Review the generated workflow document
-2. Suggest: "Run `/sdlc:design gwt <workflow>` to generate acceptance scenarios"
-3. Mention: "Vertical slices can become GitHub issues"
-
----
-
-## Action: `gwt <workflow>`
-
-Generate Given/When/Then scenarios for a workflow.
-
-```
-sdlc_generate_gwt({
-  workflowName: "<workflow name from argument>"
-})
-```
-
-**Example:** `/sdlc:design gwt Order Submission`
-
-The tool will:
-1. Load the workflow document
-2. Generate scenarios for commands, projections, and automations
-3. Create `docs/event_model/workflows/<name>/scenarios/<slice>.feature`
-
-After GWT generation:
-1. Review the generated feature files
-2. Suggest: "Run `/sdlc:design validate` to check model completeness"
-3. Mention: "These scenarios become acceptance criteria for implementation"
-
----
-
-## Action: `validate [scope]`
-
-Validate the event model for completeness and consistency.
-
-```
-sdlc_validate_model({
-  scope: "<scope from argument or 'all'>"
-})
-```
-
-**Scopes:**
-- `all` (default) - Validate everything
-- `domain` - Domain overview only
-- `workflow` - Workflow designs only
-- `scenarios` - GWT scenarios only
-
-**Example:** `/sdlc:design validate workflow`
-
-The tool checks:
-- **Naming conventions**: Events in past tense, commands imperative
-- **Completeness**: Required sections present
-- **Consistency**: References exist
-- **No implementation details**: Business language only
-
-After validation:
-1. Show summary of issues found
-2. For errors: Suggest specific fixes
-3. For warnings: Explain why they matter
-4. When valid: Suggest creating GitHub issues from slices
-
----
-
-## Action: No Arguments
-
-When called without arguments, show the current status:
-
-1. Check if domain overview exists
-2. Check for workflow documents
-3. Check for scenario files
-4. Run validation with `scope: "all"`
-
-Then recommend the next action:
-
-```
-## Event Model Status
-
-### Domain
-[ ] Domain overview not found
-    -> Run: /sdlc:design discover <domain name>
-
-### Workflows
-[x] order-submission (3 slices)
-[ ] No scenarios generated
-    -> Run: /sdlc:design gwt order-submission
-
-### Validation
-2 warnings, 0 errors
-- Event naming issue in order-submission
-- Missing glossary in domain
-
-### Recommended Next Step
-Run `/sdlc:design gwt order-submission` to generate acceptance scenarios.
-```
-
----
-
-## Event Modeling Concepts
-
-### Pattern Types
-
-| Pattern | Description | GWT Format |
-|---------|-------------|------------|
-| Command | Trigger -> Command -> Event(s) | Given=prior events, When=command, Then=events |
-| View | Events -> Projection | Given=state, When=event, Then=new state |
-| Automation | Event -> Policy -> Command | Given=policy, When=event, Then=command |
-| Translation | External -> Internal Event | Given=external data, When=received, Then=internal event |
-
-### Naming Conventions
-
-| Element | Style | Examples |
-|---------|-------|----------|
-| Events | Past tense | OrderSubmitted, PaymentReceived |
-| Commands | Imperative | SubmitOrder, ProcessPayment |
-| Read Models | Noun | OrderSummary, CustomerDashboard |
-
-### Document Structure
-
-```
-docs/event_model/
-├── domain/
-│   └── overview.md           # Actors, goals, processes, boundaries
-└── workflows/
-    └── <workflow-name>/
-        ├── overview.md       # 9-step workflow design
-        └── scenarios/
-            └── <slice>.feature  # GWT scenarios
-```
-
----
-
-## Integration with GitHub Issues
-
-| Event Model Concept | GitHub Equivalent |
-|---------------------|-------------------|
-| Workflow | Epic issue |
-| Vertical Slice | Story issue (1:1) |
-| GWT Scenarios | Acceptance Criteria |
-
-After completing event modeling:
-1. Each workflow becomes an Epic issue
-2. Each vertical slice becomes a Story issue under that Epic
-3. GWT scenarios become the acceptance criteria for each Story
-
----
-
-## Quality Standards
-
-1. **Business language only** - No technical jargon in event models
-2. **Past tense events** - OrderSubmitted, not SubmitOrder
-3. **Imperative commands** - SubmitOrder, not OrderSubmission
-4. **Concrete scenarios** - Real example values, not placeholders
-5. **Complete coverage** - Happy path + validation + edge cases
-6. **Traceable** - Every slice links to scenarios
-
----
-
-## Workflow Summary
-
-```
-1. /sdlc:design discover <domain>
-   └── Creates domain overview with actors, goals, boundaries
-
-2. /sdlc:design workflow <name>
-   └── Designs workflow with events, commands, read models, slices
-
-3. /sdlc:design gwt <workflow>
-   └── Generates GWT scenarios for acceptance criteria
-
-4. /sdlc:design validate
-   └── Checks completeness and naming conventions
-
-5. Create GitHub issues from vertical slices
-   └── Each slice = 1 story issue with GWT as acceptance criteria
-```