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.4",
"version": "0.29.5",
"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.4",
"version": "0.29.5",
"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.4",
"version": "0.29.5",
"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.4",
"version": "0.29.5",
"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
6 changes: 3 additions & 3 deletions agents/technical-designer-frontend.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ For each ADR:

1. Keep one technical question inside confirmed scope.
2. Compare every credible, materially distinct option using confirmed product value, repository fit, total complexity, maintainability, material trade-offs, and reversibility.
3. Select the smallest sufficient option whose total complexity is justified by confirmed product value.
3. Select the smallest sufficient option whose total complexity is justified by confirmed product value. Compare options at the stated quality levels, or at the implementation-approach selected level where the requirements leave one unset, and record that level in the decision.
4. Record only the selected decision as a downstream constraint. Requirements and any applicable approved UI Spec remain UI scope.
5. Keep component implementation and end-to-end flow out of the ADR. Repository-owned implementation details go to the Design Doc only when confirmed scope activates them; external release execution and organizational rollout remain outside both artifacts.

Expand Down Expand Up @@ -106,7 +106,7 @@ When existing evidence resolves the premise, update from that evidence without a

## Update Mode

Update requested sections and dependent statements. For `correction_findings`, resolve each received defect within confirmed requirements, using existing responsibilities. Accepted design decisions record the current means: remove or narrow one when the confirmed outcome, desired-future requirements, and non-goals stay true. If the confirmed outcome cannot otherwise be achieved, return the failing condition and evidence before changing that design. Preserve unaffected decisions, historical safeguards, and update history. Re-check only identifiers, Props, state, or contracts whose meaning changes. An ADR update operates on one existing ADR.
Update requested sections and dependent statements. For `correction_findings`, resolve each received defect within confirmed requirements, using existing responsibilities. Treat a finding's proposed correction as one candidate and choose in this order: remove or narrow the addition, claim, or accepted design decision it concerns, reuse existing behavior, then add or extend a mechanism only when the earlier options leave the requirement, accepted decision, or repository contract behind the finding unmet. Accepted design decisions record the current means, so removing or narrowing one is valid when the confirmed outcome, desired-future requirements, and non-goals stay true. If the confirmed outcome cannot otherwise be achieved, return the failing condition and evidence before changing that design. Preserve unaffected decisions, historical safeguards, and update history. Re-check only identifiers, Props, state, or contracts whose meaning changes. An ADR update operates on one existing ADR.

## Reverse-Engineer Mode

Expand All @@ -128,5 +128,5 @@ Document supplied inventory and existing frontend behavior as-is. Trace in-scope
- Every created ADR passes both filters and selects the lowest-total-complexity sufficient option.
- The Design Doc remains the complete frontend implementation design even when ADRs exist.
- Existing UI behavior, contracts, assumptions, states, equivalence, and verification safeguards applicable to the change remain available downstream.
- The Selected Design delivers the outcome, and every added design surface becomes necessary again when removed from its recorded evidence.
- The Selected Design delivers the outcome, and removing any added design surface leaves the origin named in its Subtraction result unmet.
- The final response is one valid JSON object.
6 changes: 3 additions & 3 deletions agents/technical-designer.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ For each ADR:

1. Keep one technical question inside confirmed scope.
2. Compare every credible, materially distinct option using confirmed product value, repository fit, total complexity, maintainability, material trade-offs, and reversibility.
3. Select the smallest sufficient option whose total complexity is justified by confirmed product value. Use relative evidence rather than fabricated estimates.
3. Select the smallest sufficient option whose total complexity is justified by confirmed product value. Use relative evidence rather than fabricated estimates. Compare options at the stated quality levels, or at the implementation-approach selected level where the requirements leave one unset, and record that level in the decision.
4. Record only the selected decision as a downstream technical constraint. The confirmed requirements remain implementation scope.
5. Keep end-to-end implementation design out of the ADR. Repository-owned implementation details go to the Design Doc only when confirmed scope activates them; external release execution and organizational rollout remain outside both artifacts.

Expand Down Expand Up @@ -112,7 +112,7 @@ When existing evidence resolves the premise, update from that evidence without a

## Update Mode

Update requested sections and dependent statements. For `correction_findings`, resolve each received defect within confirmed requirements, using existing responsibilities. Accepted design decisions record the current means: remove or narrow one when the confirmed outcome, desired-future requirements, and non-goals stay true. If the confirmed outcome cannot otherwise be achieved, return the failing condition and evidence before changing that design. Preserve unaffected decisions, historical safeguards, and update history. Re-check only identifiers or contracts whose meaning the update changes. An ADR update operates on one existing ADR; batch creation is a create-mode operation.
Update requested sections and dependent statements. For `correction_findings`, resolve each received defect within confirmed requirements, using existing responsibilities. Treat a finding's proposed correction as one candidate and choose in this order: remove or narrow the addition, claim, or accepted design decision it concerns, reuse existing behavior, then add or extend a mechanism only when the earlier options leave the requirement, accepted decision, or repository contract behind the finding unmet. Accepted design decisions record the current means, so removing or narrowing one is valid when the confirmed outcome, desired-future requirements, and non-goals stay true. If the confirmed outcome cannot otherwise be achieved, return the failing condition and evidence before changing that design. Preserve unaffected decisions, historical safeguards, and update history. Re-check only identifiers or contracts whose meaning the update changes. An ADR update operates on one existing ADR; batch creation is a create-mode operation.

## Reverse-Engineer Mode

Expand All @@ -134,5 +134,5 @@ Document supplied inventory and existing behavior as-is. Trace each in-scope ent
- Every created ADR passes both filters and selects the lowest-total-complexity sufficient option.
- The Design Doc remains the complete implementation design even when ADRs exist.
- Existing-behavior, contract, assumption, equivalence, and verification safeguards applicable to the change remain available to downstream consumers.
- The Selected Design delivers the outcome, and every added design surface becomes necessary again when removed from its recorded evidence.
- The Selected Design delivers the outcome, and removing any added design surface leaves the origin named in its Subtraction result unmet.
- The final 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.4",
"version": "0.29.5",
"author": {
"name": "Shinsuke Kagawa",
"url": "https://github.com/shinpr"
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -74,10 +74,7 @@ How quality is enforced in the change area. Each item is either adopted (will be

#### Non-Functional Requirements

- **Performance**: [Response time, throughput requirements]
- **Scalability**: [Requirements for handling increased load]
- **Reliability**: [Error rate, availability requirements]
- **Maintainability**: [Code readability and changeability]
- **[Quality attribute]**: [level] - Source: [requirement that states it | selected in Design Convergence because the requirements leave it unset]

## Acceptance Criteria (AC) - EARS Format

Expand Down Expand Up @@ -201,7 +198,7 @@ For each added design surface—user decision, setting, mode, concept, output, p
- **Addition**: [selected design surface]
- **Current evidence**: [requirement, accepted decision, verified constraint, observed problem, or evidence-backed material risk]
- **Lower-surface insufficiency**: [why reuse, derivation, on-demand computation, or current-boundary ownership does not satisfy the same condition]
- **Subtraction result**: [confirmed outcome, required boundary, or proof that becomes unmet when removed]
- **Subtraction result**: [confirmed outcome, required boundary, or proof that becomes unmet when removed, traced to its originating requirement, accepted decision, or repository rule or contract]

Use `None — existing design surface is sufficient` when the selected design adds none of these surfaces.

Expand Down
13 changes: 2 additions & 11 deletions dev-skills/skills/implementation-approach/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,9 +31,9 @@ Stop when another current-state fact cannot change responsibility, reuse, option
Complete these steps in order before selecting an implementation strategy:

1. **Existing-Surface Baseline**: Form the simplest end-to-end path that delivers the current outcome through existing responsibilities. Explicit requirements and accepted decisions are binding; suggested mechanisms remain candidates.
2. **Evidence Check**: Test that path against current requirements, verified constraints, observed in-scope problems, and evidence-backed material risks. Keep only the unmet conditions that can change the selected design.
2. **Evidence Check**: Test that path against current requirements, verified constraints, observed in-scope problems, and evidence-backed material risks. Keep only the unmet conditions that can change the selected design. Where the requirements leave a quality level unset, such as performance, freshness, consistency, availability, or protection beyond the required trust boundary, test against the lowest level that still delivers the outcome and record it as the selected level.
3. **Targeted Comparison**: For each unmet condition, test reuse, derivation from existing data, on-demand computation, or responsibility at the current caller or boundary before adding design surface. Compare viable choices by total complexity across the dimensions that materially differ: user decisions, settings, modes, concepts, outputs, persistent state, implementation paths, UX, runtime, implementation, testing, documentation, and maintenance. Select the lowest-total-complexity choice that satisfies the condition.
4. **Subtraction Check**: Remove each proposed addition and re-test its governing condition. Retain it only when the confirmed outcome, a required boundary, or necessary proof becomes unmet.
4. **Subtraction Check**: Remove each proposed addition and re-test its governing condition. Retain it only when the confirmed outcome, a required boundary, or necessary proof becomes unmet at its origin (a confirmed requirement, an accepted decision, or a repository rule or contract); a criterion, invariant, or constraint that a workflow artifact derived from that origin is narrowed to what the origin requires instead.

Classify supporting claims as observed, inferred, or unknown. Route an unknown that blocks the next step as an exact evidence prerequisite; the caller's value-boundary and irreversible-action gates determine whether user interaction is required.

Expand Down Expand Up @@ -79,13 +79,6 @@ Evaluate only risk categories for which current evidence can change the strategy
```yaml
Technical Risks: System impact, data consistency, performance degradation, integration complexity
Operational Risks: Service availability, deployment downtime, process changes, rollback procedures
Project Risks: Schedule delays, learning costs, quality achievement, team coordination
```

#### Risk Control Strategies
```yaml
Preventive Measures: Phased migration, parallel operation verification, integration/regression tests, monitoring setup
Incident Response: Rollback procedures, log/metrics preparation, communication system, service continuation procedures
```

### Phase 5: Decision-Relevant Constraint Compatibility
Expand All @@ -98,8 +91,6 @@ Check only constraints evidenced by the governing requirements, repository, exte
```yaml
Technical Constraints: Library compatibility, resource capacity, mandatory requirements, numerical targets
Temporal Constraints: Deadlines/priorities, dependencies, milestones, learning periods
Resource Constraints: Team/skills, work hours/systems, budget, external contracts
Business Constraints: Market launch timing, customer impact, regulatory compliance
```

### Phase 6: Implementation Approach Decision
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.4",
"version": "0.29.5",
"author": {
"name": "Shinsuke Kagawa",
"url": "https://github.com/shinpr"
Expand Down
6 changes: 3 additions & 3 deletions dev-workflows-frontend/agents/technical-designer-frontend.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ For each ADR:

1. Keep one technical question inside confirmed scope.
2. Compare every credible, materially distinct option using confirmed product value, repository fit, total complexity, maintainability, material trade-offs, and reversibility.
3. Select the smallest sufficient option whose total complexity is justified by confirmed product value.
3. Select the smallest sufficient option whose total complexity is justified by confirmed product value. Compare options at the stated quality levels, or at the implementation-approach selected level where the requirements leave one unset, and record that level in the decision.
4. Record only the selected decision as a downstream constraint. Requirements and any applicable approved UI Spec remain UI scope.
5. Keep component implementation and end-to-end flow out of the ADR. Repository-owned implementation details go to the Design Doc only when confirmed scope activates them; external release execution and organizational rollout remain outside both artifacts.

Expand Down Expand Up @@ -106,7 +106,7 @@ When existing evidence resolves the premise, update from that evidence without a

## Update Mode

Update requested sections and dependent statements. For `correction_findings`, resolve each received defect within confirmed requirements, using existing responsibilities. Accepted design decisions record the current means: remove or narrow one when the confirmed outcome, desired-future requirements, and non-goals stay true. If the confirmed outcome cannot otherwise be achieved, return the failing condition and evidence before changing that design. Preserve unaffected decisions, historical safeguards, and update history. Re-check only identifiers, Props, state, or contracts whose meaning changes. An ADR update operates on one existing ADR.
Update requested sections and dependent statements. For `correction_findings`, resolve each received defect within confirmed requirements, using existing responsibilities. Treat a finding's proposed correction as one candidate and choose in this order: remove or narrow the addition, claim, or accepted design decision it concerns, reuse existing behavior, then add or extend a mechanism only when the earlier options leave the requirement, accepted decision, or repository contract behind the finding unmet. Accepted design decisions record the current means, so removing or narrowing one is valid when the confirmed outcome, desired-future requirements, and non-goals stay true. If the confirmed outcome cannot otherwise be achieved, return the failing condition and evidence before changing that design. Preserve unaffected decisions, historical safeguards, and update history. Re-check only identifiers, Props, state, or contracts whose meaning changes. An ADR update operates on one existing ADR.

## Reverse-Engineer Mode

Expand All @@ -128,5 +128,5 @@ Document supplied inventory and existing frontend behavior as-is. Trace in-scope
- Every created ADR passes both filters and selects the lowest-total-complexity sufficient option.
- The Design Doc remains the complete frontend implementation design even when ADRs exist.
- Existing UI behavior, contracts, assumptions, states, equivalence, and verification safeguards applicable to the change remain available downstream.
- The Selected Design delivers the outcome, and every added design surface becomes necessary again when removed from its recorded evidence.
- The Selected Design delivers the outcome, and removing any added design surface leaves the origin named in its Subtraction result unmet.
- The final response is one valid JSON object.
Original file line number Diff line number Diff line change
Expand Up @@ -74,10 +74,7 @@ How quality is enforced in the change area. Each item is either adopted (will be

#### Non-Functional Requirements

- **Performance**: [Response time, throughput requirements]
- **Scalability**: [Requirements for handling increased load]
- **Reliability**: [Error rate, availability requirements]
- **Maintainability**: [Code readability and changeability]
- **[Quality attribute]**: [level] - Source: [requirement that states it | selected in Design Convergence because the requirements leave it unset]

## Acceptance Criteria (AC) - EARS Format

Expand Down Expand Up @@ -201,7 +198,7 @@ For each added design surface—user decision, setting, mode, concept, output, p
- **Addition**: [selected design surface]
- **Current evidence**: [requirement, accepted decision, verified constraint, observed problem, or evidence-backed material risk]
- **Lower-surface insufficiency**: [why reuse, derivation, on-demand computation, or current-boundary ownership does not satisfy the same condition]
- **Subtraction result**: [confirmed outcome, required boundary, or proof that becomes unmet when removed]
- **Subtraction result**: [confirmed outcome, required boundary, or proof that becomes unmet when removed, traced to its originating requirement, accepted decision, or repository rule or contract]

Use `None — existing design surface is sufficient` when the selected design adds none of these surfaces.

Expand Down
Loading
Loading