Skip to content

Commit e560072

Browse files
committed
Highlight that all commands work without arguments
Commands auto-extract task descriptions from conversation context and auto-detect task types. Added context-aware usage examples throughout README, commands reference, and workflow docs.
1 parent cd827af commit e560072

File tree

3 files changed

+46
-15
lines changed

3 files changed

+46
-15
lines changed

README.md

Lines changed: 30 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -40,28 +40,53 @@ This scans your codebase and creates `.maister/` with auto-detected coding stand
4040
/maister:work "Add user profile page with avatar upload"
4141
```
4242

43+
Or just discuss your task with Claude and then run:
44+
45+
```
46+
/maister:work
47+
```
48+
49+
The plugin picks up context from your conversation — no arguments needed.
50+
4351
## How It Works
4452

45-
1. You describe a task in natural language
53+
1. You describe a task — either as an argument or just in conversation
4654
2. The plugin classifies it (feature, bug, enhancement, etc.) and proposes a workflow
4755
3. You confirm, and it guides you through phases: **requirements → spec → plan → implement → verify**
4856
4. At each phase, it asks for your input and decisions (or pass `--yolo` for continuous execution)
4957
5. You get tested, verified code with a detailed work log
5058

5159
All artifacts are saved in `.maister/tasks/` organized by type and date.
5260

61+
### Context-Aware Commands
62+
63+
Every workflow command works without arguments. The plugin reads your current conversation to extract the task description and auto-detect the task type:
64+
65+
```
66+
You: "The login page throws a 500 error when the session expires"
67+
You: /maister:development-new
68+
→ Auto-detects: bug fix, extracts description from conversation
69+
```
70+
71+
```
72+
You: /maister:standards-update
73+
→ Scans conversation for patterns like "we always use..." or "prefer X over Y"
74+
```
75+
76+
You can always be explicit when you prefer — arguments and flags simply override the auto-detection.
77+
5378
## Supported Workflows
5479

5580
| Type | Command | Use When |
5681
|------|---------|----------|
57-
| **Feature** | `/maister:development-new --type=feature` | Adding new capabilities |
58-
| **Bug Fix** | `/maister:development-new --type=bug` | Fixing defects with TDD Red→Green |
59-
| **Enhancement** | `/maister:development-new --type=enhancement` | Improving existing features |
82+
| **Feature** | `/maister:development-new` | Adding new capabilities |
83+
| **Bug Fix** | `/maister:development-new` | Fixing defects with TDD Red→Green |
84+
| **Enhancement** | `/maister:development-new` | Improving existing features |
6085
| **Performance** | `/maister:performance-new` | Optimizing speed or resource usage |
6186
| **Migration** | `/maister:migration-new` | Changing technologies or patterns |
6287
| **Research** | `/maister:research-new` | Investigating questions or gathering requirements |
6388

64-
Or just use `/maister:work "description"` and let the plugin classify automatically.
89+
Task type (feature/bug/enhancement) is auto-detected from context. Override with `--type=feature|bug|enhancement` if needed. Or use `/maister:work` as a single entry point that routes to the right workflow.
6590

6691
## Standards-Aware Development
6792

docs/commands.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@
66

77
Auto-classifies your task and routes to the appropriate workflow. Accepts:
88

9+
- **No arguments**: Extracts the task from your current conversation context
910
- Task description: `/maister:work "Add user profile page"`
1011
- Task folder path: `/maister:work .maister/tasks/new-features/2026-02-17-user-profile` (resumes)
1112
- GitHub issue URL: `/maister:work https://github.com/org/repo/issues/42`
@@ -18,7 +19,7 @@ The plugin classifies the task type with confidence scoring, asks for confirmati
1819

1920
### `/maister:development-new [description]`
2021

21-
Starts the unified development workflow (14 adaptive phases).
22+
Starts the unified development workflow (14 adaptive phases). All arguments are optional — when run without a description, the plugin extracts it from your current conversation. Task type (bug/enhancement/feature) is auto-detected from context when `--type` is omitted.
2223

2324
| Flag | Description |
2425
|------|-------------|
@@ -58,7 +59,7 @@ Resume an interrupted development workflow from where it left off.
5859

5960
### `/maister:performance-new [description]`
6061

61-
Starts performance optimization with static bottleneck analysis (9 phases). Detects N+1 queries, missing indexes, O(n^2) algorithms, blocking I/O, and memory leak patterns.
62+
Starts performance optimization with static bottleneck analysis (9 phases). Can be run without arguments — the plugin extracts the optimization target from your conversation. Detects N+1 queries, missing indexes, O(n^2) algorithms, blocking I/O, and memory leak patterns.
6263

6364
| Flag | Description |
6465
|------|-------------|
@@ -81,7 +82,7 @@ You can optionally provide profiling data (flame graphs, APM screenshots) — th
8182

8283
### `/maister:migration-new [description]`
8384

84-
Starts migration workflow (8 phases) with mandatory rollback planning and risk assessment.
85+
Starts migration workflow (8 phases) with mandatory rollback planning and risk assessment. Can be run without arguments — the plugin extracts migration details from your conversation.
8586

8687
| Flag | Description |
8788
|------|-------------|
@@ -104,7 +105,7 @@ Starts migration workflow (8 phases) with mandatory rollback planning and risk a
104105

105106
### `/maister:research-new [question]`
106107

107-
Starts research workflow (8 phases) with multi-source gathering, synthesis, and optional solution brainstorming.
108+
Starts research workflow (8 phases) with multi-source gathering, synthesis, and optional solution brainstorming. Can be run without arguments — the plugin extracts the research question from your conversation.
108109

109110
| Flag | Description |
110111
|------|-------------|
@@ -197,7 +198,7 @@ Presents findings in confidence tiers (high/medium/low) for review before applyi
197198

198199
### `/maister:standards-update [description]`
199200

200-
Update or create standards from conversation context or explicit description. Scans recent conversation for patterns like "we should always...", "our convention is...", "prefer X over Y".
201+
Update or create standards from conversation context or explicit description. When run without arguments, scans your current conversation for standards patterns like "we should always...", "our convention is...", "prefer X over Y" and proposes them as new standards.
201202

202203
---
203204

docs/workflows.md

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,11 +7,13 @@ Maister provides six workflow types, each with phases tailored to its needs. All
77
The unified development workflow handles features, enhancements, and bug fixes through a 14-phase adaptive pipeline. Phases activate or skip based on task type.
88

99
```
10-
/maister:development-new "Add two-factor authentication" --type=feature
10+
/maister:development-new
11+
/maister:development-new "Add two-factor authentication"
1112
/maister:development-new "Fix login timeout" --type=bug
12-
/maister:development-new "Add CSV export to reports" --type=enhancement
1313
```
1414

15+
When run without arguments, the plugin extracts the task description from your conversation and auto-detects the type (feature, bug, or enhancement). Use `--type=` only when you want to override the auto-detection.
16+
1517
**Flags**: `--type=bug|enhancement|feature`, `--yolo`, `--e2e`, `--user-docs`, `--code-review`, `--research=PATH`, `--from=PHASE`
1618

1719
### Phases
@@ -58,7 +60,8 @@ Resume phases: `analysis`, `gap`, `spec`, `plan`, `implement`, `verify`
5860
Static code analysis to detect bottlenecks, followed by standard spec/plan/implement/verify pipeline.
5961

6062
```
61-
/maister:performance-new "Optimize dashboard loading time" [--yolo]
63+
/maister:performance-new
64+
/maister:performance-new "Optimize dashboard loading time" --yolo
6265
```
6366

6467
### Phases
@@ -92,7 +95,8 @@ Resume phases: `analysis`, `specification`, `planning`, `implementation`, `verif
9295
Technology, data, and architecture migrations with rollback planning and risk assessment.
9396

9497
```
95-
/maister:migration-new "Migrate from REST to GraphQL" [--yolo] [--type=TYPE]
98+
/maister:migration-new
99+
/maister:migration-new "Migrate from REST to GraphQL" --type=code
96100
```
97101

98102
**Migration types**: `code`, `data`, `architecture`, `general`
@@ -131,7 +135,8 @@ Resume phases: `analysis`, `target`, `spec`, `plan`, `execute`, `verify`, `docs`
131135
Multi-source research with synthesis, optional solution brainstorming, and high-level design.
132136

133137
```
134-
/maister:research-new "What authentication approach fits our architecture?" [--yolo] [--type=TYPE]
138+
/maister:research-new
139+
/maister:research-new "What authentication approach fits our architecture?" --type=technical
135140
```
136141

137142
**Research types**: `technical`, `requirements`, `literature`, `mixed`

0 commit comments

Comments
 (0)