@konductro/claude-plugin 2.1.0 → 2.1.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/package.json
CHANGED
package/servers/konductro-api.js
CHANGED
|
@@ -297,7 +297,7 @@ server.tool(
|
|
|
297
297
|
title: z.string().describe('Task title'),
|
|
298
298
|
description: z.string().describe('Technical description of the task'),
|
|
299
299
|
repositoryId: z.string().describe('Repository ID from the context'),
|
|
300
|
-
type: z.
|
|
300
|
+
type: z.string().trim().max(24).optional().describe('Short free-text tech tag derived from the repo stack (e.g. C#, PHP, Node, Java, UI, Infra); one token, max 24 chars, no fixed list'),
|
|
301
301
|
acceptanceCriteria: z.array(z.string()).default([]).describe('Technical acceptance criteria'),
|
|
302
302
|
architecturalNotes: z.array(z.string()).default([]).describe('Implementation notes for the agent'),
|
|
303
303
|
componentPath: z.string().optional().nullable().describe('Primary file/directory path for this task'),
|
|
@@ -45,7 +45,7 @@ Based on the story requirements and your codebase understanding, plan the tasks.
|
|
|
45
45
|
- **Execution order** — what needs to be built first (e.g., schema before API before UI)
|
|
46
46
|
- **Task boundaries** — each task should be a single PR, touching one concern
|
|
47
47
|
- **Repository assignment** — which repo does each task belong to
|
|
48
|
-
- **Task type** — `
|
|
48
|
+
- **Task type** — a short free-text tech tag derived from the target repo's stack (e.g. `C#`, `PHP`, `Node`, `Java`, `Angular`, `UI`, `Infra`). One canonical token, max 24 chars — there is no fixed list; match the repo's actual language/domain.
|
|
49
49
|
- **Dependencies between tasks** — task 2 may depend on task 1's API
|
|
50
50
|
|
|
51
51
|
Present your proposed decomposition to the user before submitting.
|
|
@@ -57,7 +57,7 @@ For each task, produce the full developer brief — this is the complete impleme
|
|
|
57
57
|
1. **title** — short, action-oriented (e.g., "Add sprint.projectId column and migration")
|
|
58
58
|
2. **description** — technical description of what to build and how, referencing specific files, patterns, and APIs
|
|
59
59
|
3. **repositoryId** — from the context (the repo this task targets)
|
|
60
|
-
4. **type** — `
|
|
60
|
+
4. **type** — short free-text tech tag from the repo's stack (e.g. `C#`, `PHP`, `Node`, `Java`, `Angular`, `UI`, `Infra`); one canonical token, max 24 chars, no fixed list
|
|
61
61
|
5. **acceptanceCriteria** — specific, testable criteria for this task
|
|
62
62
|
6. **architecturalNotes** — implementation hints, patterns to follow, gotchas
|
|
63
63
|
7. **componentPath** — primary file or directory being changed
|