Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions .claude-plugin/marketplace.json
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@
"name": "dev-workflows",
"source": "./dev-workflows",
"strict": true,
"version": "0.29.3",
"version": "0.29.4",
"description": "Skills + Subagents for backend development - Use skills for coding guidance, or run recipe workflows for full orchestrated agentic coding with specialized agents",
"author": {
"name": "Shinsuke Kagawa",
Expand Down Expand Up @@ -80,7 +80,7 @@
"name": "dev-workflows-frontend",
"source": "./dev-workflows-frontend",
"strict": true,
"version": "0.29.3",
"version": "0.29.4",
"description": "Skills + Subagents for React/TypeScript - Use skills for coding guidance, or run recipe workflows for full orchestrated agentic coding with specialized agents",
"author": {
"name": "Shinsuke Kagawa",
Expand Down Expand Up @@ -149,7 +149,7 @@
"name": "dev-workflows-fullstack",
"source": "./dev-workflows-fullstack",
"strict": true,
"version": "0.29.3",
"version": "0.29.4",
"description": "Skills + Subagents for fullstack development (backend + React/TypeScript) - Use skills for coding guidance, or run recipe workflows for full orchestrated agentic coding with specialized agents",
"author": {
"name": "Shinsuke Kagawa",
Expand Down Expand Up @@ -235,7 +235,7 @@
"name": "dev-skills",
"source": "./dev-skills",
"strict": true,
"version": "0.29.3",
"version": "0.29.4",
"description": "Lightweight skills for users with existing workflows - coding best practices, testing principles, and design guidelines without recipe workflows or agents",
"author": {
"name": "Shinsuke Kagawa",
Expand Down
3 changes: 1 addition & 2 deletions agents/prd-creator.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Before acting, map the preloaded skills to concrete rules for this task. Follow
3. Define success metrics
4. Clarify scope (what's included/excluded)
5. Verify consistency with existing systems
6. **Verify decision-changing external value evidence**: Use WebSearch when current market, competitor, regulatory, or compatibility facts can change business value or MVP scope and the user, accepted contracts, usage evidence, and existing PRDs do not already determine that decision. Record the authoritative source and the decision it affects
6. **Verify decision-changing external value evidence**: Use WebSearch when current market, competitor, or compatibility facts can change business value or MVP scope and the user, accepted contracts, usage evidence, and existing PRDs leave that decision open. Record the authoritative source and the decision it affects

## When PRD is Needed

Expand Down Expand Up @@ -122,7 +122,6 @@ PRDs focus solely on "what to build." Implementation phases and task decompositi
- In reverse-engineer mode, preserve observed measures and distinguish unknown business goals; derive no new target from a template.

### 4. Completeness Check
- Include all stakeholder perspectives
- Consider edge cases
- Clarify constraints

Expand Down
14 changes: 5 additions & 9 deletions agents/requirement-analyzer.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,9 +28,9 @@ Start from the product responsibility the outcome implies, then scan broadly and

Inspect a located responsibility further only when leaving it unchanged can affect the outcome, requirement confirmation, relative cost, or the analysis target. Read the minimum evidence needed to state its current treatment and the consequence a user would observe, then record both in `responsibilityBoundaries`. Stop expanding a branch when its remaining findings could only refine design or implementation.

### 2. Form Cost and Question Evidence
### 2. Form Cost Evidence

Summarize relative cost from observed boundaries, reuse, persistence or contract changes, and verification support. Record an unknown or question only when its answer can change the outcome, current requirements, exclusions, Structural Scale, or the analysis target, and the repository cannot resolve it.
Summarize relative cost from observed boundaries, reuse, persistence or contract changes, and verification support. Record an unknown only when it can change the outcome, current requirements, Structural Scale, or the analysis target, and the repository cannot resolve it.

Return the evidence for orchestrator judgment. The orchestrator assigns convergence readiness, Structural Scale, ADR need, and implementation scope.

Expand All @@ -55,21 +55,17 @@ Return exactly one JSON object:
"drivers": [
{"kind": "observed|inferred", "fact": "structural cost fact", "source": "request or path"}
],
"unknowns": ["fact that can change relative cost"]
},
"questions": [
{"decision": "outcome|requirement|exclusion|scale|analysis_target", "question": "specific unresolved question", "effect": "what changes based on the answer"}
]
"unknowns": ["fact the repository cannot resolve that can change cost, scope, or scale"]
}
}
```

## Completion Check

- Scope and cost evidence is shallow, compact, and source-backed.
- Each retained responsibility boundary states its current treatment and the consequence a user would observe.
- Every user-facing or operational responsibility a cost driver or question relies on has a source-backed boundary entry, or is recorded as an unknown.
- Every user-facing or operational responsibility a cost driver relies on has a source-backed boundary entry, or is recorded as an unknown.
- `executionRoute.status: evident` is backed by one representative route inside one responsibility; an empty search or absence of alternatives remains `unresolved`.
- Every question names the decision its answer can change.
- Remaining investigation belongs to later codebase analysis or design.
- Product requirements and exclusions remain assigned to the user; convergence readiness, Structural Scale, ADR, and implementation-scope decisions remain assigned to the orchestrator.
- The response is one valid JSON object.
2 changes: 1 addition & 1 deletion dev-skills/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "dev-skills",
"description": "Lightweight skills for users with existing workflows - coding best practices, testing principles, and design guidelines without recipe workflows or agents",
"version": "0.29.3",
"version": "0.29.4",
"author": {
"name": "Shinsuke Kagawa",
"url": "https://github.com/shinpr"
Expand Down
2 changes: 1 addition & 1 deletion dev-skills/skills/documentation-criteria/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ This file holds the routing decision: which documents a change requires and wher

Each document fixes one class of decision that the repository alone cannot supply. An unfilled section becomes a guess made later by the consumer named below, with no record of what was assumed.

- **PRD** — Fixes the business outcome and the acceptance criteria later work traces to. Its AC IDs are the traceability keys that the Design Doc, UI Spec, and test selection reuse; without them each consumer re-derives requirements from prose and the link between a test and the value it protects is lost. Implementation details belong to the Design Doc, selection rationale to an ADR, phases and task breakdown to the Work Plan.
- **PRD** — Fixes the business outcome and the acceptance criteria later work traces to. Its AC IDs are the traceability keys that the Design Doc, UI Spec, and test selection reuse; without them each consumer re-derives requirements from prose and the link between a test and the value it protects is lost. Implementation details belong to the Design Doc, selection rationale to an ADR, phases and task breakdown to the Work Plan. Later design, review, and test selection treat its content as governing, so a precondition held outside the repository change, such as release execution or organizational approval, appears in it only when the user's wording raises it.

- **ADR** — Records one durable technical choice and the options it beat, so later work can tell a deliberate decision from an accident. Without it a future change either re-runs the same comparison or silently reverses it. `Accepted` records the currently selected means, not an obligation to retain it: when later evidence supports a smaller sufficient choice, update or supersede the decision while the confirmed outcome, desired-future requirements, and non-goals remain true. End-to-end implementation design belongs to the Design Doc, schedule and repository tasks to the Work Plan.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -124,7 +124,7 @@ State observable success for the confirmed outcome. Include only sourced quantit
- [Prerequisite requiring validation 2]

### Risks and Mitigation
Include only evidenced product or delivery risks that can change scope, success criteria, sequencing, or acceptance.
Include only evidenced product risks that can change scope, success criteria, or acceptance.

| Risk | Impact | Probability | Mitigation |
|------|--------|-------------|------------|
Expand Down
2 changes: 1 addition & 1 deletion dev-skills/skills/requirement-convergence/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ Render this shape at every requirements confirmation stop, whether or not the he
|---------|----------|
| **Confirmed scope** | The requirements and exclusions the user has already selected, in the user's wording |
| **Decision evidence** | Each material observed fact with its source, followed by what that fact can change about scope, outcome, or cost |
| **User decisions** | Each unresolved product, UX, or operational question, followed by the scope, outcome, or cost effects of its materially different answers |
| **User decisions** | One question per convergence field below `ready` (Hearing Protocol Step 1), followed by the scope, outcome, or cost effects of its materially different answers |
| **Workflow** | Rough cost band with the unknowns that remain, Structural Scale, and the selected document and workflow route |

Keeping the first three sections separate is what makes the decision informable: merged, the reader cannot tell which line is the user's own settled boundary, which is a repository observation, and which is still open.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,8 @@ Evaluation requests, speculative ideas, and prescribed mechanisms stay in active

Flattening current state, desired future, and candidates into one requirement list makes a bloated plan look coherent because every item then reads as equally required. Label each build-relevant item; ask when its current-state or desired-future role is unclear rather than inferring it.

An item is build-relevant when the repository change can satisfy it. A precondition held outside that change, such as legal or policy review, contract execution, release execution, or organizational approval, enters `requirements[]` and the hearing only when the user's wording raises it.

## nonGoals[]

Capabilities deliberately excluded from this change, authored by the user.
Expand Down
2 changes: 1 addition & 1 deletion dev-workflows-frontend/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "dev-workflows-frontend",
"description": "Skills + Subagents for React/TypeScript - Use skills for coding guidance, or run recipe workflows for full orchestrated agentic coding with specialized agents",
"version": "0.29.3",
"version": "0.29.4",
"author": {
"name": "Shinsuke Kagawa",
"url": "https://github.com/shinpr"
Expand Down
3 changes: 1 addition & 2 deletions dev-workflows-frontend/agents/prd-creator.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Before acting, map the preloaded skills to concrete rules for this task. Follow
3. Define success metrics
4. Clarify scope (what's included/excluded)
5. Verify consistency with existing systems
6. **Verify decision-changing external value evidence**: Use WebSearch when current market, competitor, regulatory, or compatibility facts can change business value or MVP scope and the user, accepted contracts, usage evidence, and existing PRDs do not already determine that decision. Record the authoritative source and the decision it affects
6. **Verify decision-changing external value evidence**: Use WebSearch when current market, competitor, or compatibility facts can change business value or MVP scope and the user, accepted contracts, usage evidence, and existing PRDs leave that decision open. Record the authoritative source and the decision it affects

## When PRD is Needed

Expand Down Expand Up @@ -122,7 +122,6 @@ PRDs focus solely on "what to build." Implementation phases and task decompositi
- In reverse-engineer mode, preserve observed measures and distinguish unknown business goals; derive no new target from a template.

### 4. Completeness Check
- Include all stakeholder perspectives
- Consider edge cases
- Clarify constraints

Expand Down
14 changes: 5 additions & 9 deletions dev-workflows-frontend/agents/requirement-analyzer.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,9 +28,9 @@ Start from the product responsibility the outcome implies, then scan broadly and

Inspect a located responsibility further only when leaving it unchanged can affect the outcome, requirement confirmation, relative cost, or the analysis target. Read the minimum evidence needed to state its current treatment and the consequence a user would observe, then record both in `responsibilityBoundaries`. Stop expanding a branch when its remaining findings could only refine design or implementation.

### 2. Form Cost and Question Evidence
### 2. Form Cost Evidence

Summarize relative cost from observed boundaries, reuse, persistence or contract changes, and verification support. Record an unknown or question only when its answer can change the outcome, current requirements, exclusions, Structural Scale, or the analysis target, and the repository cannot resolve it.
Summarize relative cost from observed boundaries, reuse, persistence or contract changes, and verification support. Record an unknown only when it can change the outcome, current requirements, Structural Scale, or the analysis target, and the repository cannot resolve it.

Return the evidence for orchestrator judgment. The orchestrator assigns convergence readiness, Structural Scale, ADR need, and implementation scope.

Expand All @@ -55,21 +55,17 @@ Return exactly one JSON object:
"drivers": [
{"kind": "observed|inferred", "fact": "structural cost fact", "source": "request or path"}
],
"unknowns": ["fact that can change relative cost"]
},
"questions": [
{"decision": "outcome|requirement|exclusion|scale|analysis_target", "question": "specific unresolved question", "effect": "what changes based on the answer"}
]
"unknowns": ["fact the repository cannot resolve that can change cost, scope, or scale"]
}
}
```

## Completion Check

- Scope and cost evidence is shallow, compact, and source-backed.
- Each retained responsibility boundary states its current treatment and the consequence a user would observe.
- Every user-facing or operational responsibility a cost driver or question relies on has a source-backed boundary entry, or is recorded as an unknown.
- Every user-facing or operational responsibility a cost driver relies on has a source-backed boundary entry, or is recorded as an unknown.
- `executionRoute.status: evident` is backed by one representative route inside one responsibility; an empty search or absence of alternatives remains `unresolved`.
- Every question names the decision its answer can change.
- Remaining investigation belongs to later codebase analysis or design.
- Product requirements and exclusions remain assigned to the user; convergence readiness, Structural Scale, ADR, and implementation-scope decisions remain assigned to the orchestrator.
- The response is one valid JSON object.
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ This file holds the routing decision: which documents a change requires and wher

Each document fixes one class of decision that the repository alone cannot supply. An unfilled section becomes a guess made later by the consumer named below, with no record of what was assumed.

- **PRD** — Fixes the business outcome and the acceptance criteria later work traces to. Its AC IDs are the traceability keys that the Design Doc, UI Spec, and test selection reuse; without them each consumer re-derives requirements from prose and the link between a test and the value it protects is lost. Implementation details belong to the Design Doc, selection rationale to an ADR, phases and task breakdown to the Work Plan.
- **PRD** — Fixes the business outcome and the acceptance criteria later work traces to. Its AC IDs are the traceability keys that the Design Doc, UI Spec, and test selection reuse; without them each consumer re-derives requirements from prose and the link between a test and the value it protects is lost. Implementation details belong to the Design Doc, selection rationale to an ADR, phases and task breakdown to the Work Plan. Later design, review, and test selection treat its content as governing, so a precondition held outside the repository change, such as release execution or organizational approval, appears in it only when the user's wording raises it.

- **ADR** — Records one durable technical choice and the options it beat, so later work can tell a deliberate decision from an accident. Without it a future change either re-runs the same comparison or silently reverses it. `Accepted` records the currently selected means, not an obligation to retain it: when later evidence supports a smaller sufficient choice, update or supersede the decision while the confirmed outcome, desired-future requirements, and non-goals remain true. End-to-end implementation design belongs to the Design Doc, schedule and repository tasks to the Work Plan.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -124,7 +124,7 @@ State observable success for the confirmed outcome. Include only sourced quantit
- [Prerequisite requiring validation 2]

### Risks and Mitigation
Include only evidenced product or delivery risks that can change scope, success criteria, sequencing, or acceptance.
Include only evidenced product risks that can change scope, success criteria, or acceptance.

| Risk | Impact | Probability | Mitigation |
|------|--------|-------------|------------|
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ Render this shape at every requirements confirmation stop, whether or not the he
|---------|----------|
| **Confirmed scope** | The requirements and exclusions the user has already selected, in the user's wording |
| **Decision evidence** | Each material observed fact with its source, followed by what that fact can change about scope, outcome, or cost |
| **User decisions** | Each unresolved product, UX, or operational question, followed by the scope, outcome, or cost effects of its materially different answers |
| **User decisions** | One question per convergence field below `ready` (Hearing Protocol Step 1), followed by the scope, outcome, or cost effects of its materially different answers |
| **Workflow** | Rough cost band with the unknowns that remain, Structural Scale, and the selected document and workflow route |

Keeping the first three sections separate is what makes the decision informable: merged, the reader cannot tell which line is the user's own settled boundary, which is a repository observation, and which is still open.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,8 @@ Evaluation requests, speculative ideas, and prescribed mechanisms stay in active

Flattening current state, desired future, and candidates into one requirement list makes a bloated plan look coherent because every item then reads as equally required. Label each build-relevant item; ask when its current-state or desired-future role is unclear rather than inferring it.

An item is build-relevant when the repository change can satisfy it. A precondition held outside that change, such as legal or policy review, contract execution, release execution, or organizational approval, enters `requirements[]` and the hearing only when the user's wording raises it.

## nonGoals[]

Capabilities deliberately excluded from this change, authored by the user.
Expand Down
Loading
Loading