Files

T

soroush.asadi 4416d99360 Any seat can be AI-staffed: engineer/designer/analyst atoms + role-aware seat suggestions

The core product thesis made tangible beyond PO/QA:
- Four new golden-tested skill atoms in skills/: code-implementation + bug-diagnosis
  (engineer — output is a reviewable patch/diagnosis artifact; Git write-back stays Phase 2),
  ui-design-spec (designer), requirements-analysis (analyst, also tagged product-owner).
  The catalogue now spans five roles with eight atoms.
- Seat configurator: SuggestedSkills — maps the seat's free-text role name to skill role
  tags and offers the matching set one click ("Use set"). Any role name → staffed with AI.
- AnyRoleSeatTests: an "Backend Engineer" seat (Edison, gated) runs the same pipeline —
  skills assemble, implement-code/Draft parsed, proposal held in the review inbox like any
  governed action. SkillSyncTests updated for the larger catalogue.

Verified: IntegrationTests 44/44, client build green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-06-10 13:57:10 +03:30

1.6 KiB

Raw Blame History

id, name, version, summary, roles, inputs, outputs, actions, tools, context, visibility, min_tier, golden_tests

name

version

summary

roles

inputs

outputs

actions

tools

context

visibility

min_tier

golden_tests

bug-diagnosis

Bug Diagnosis

1.0.0

From a bug report and code context, find the root cause and propose the fix.

engineer

A bug report (symptoms, repro steps) and any relevant code or logs attached to the task.

Root-cause analysis, the proposed fix as a patch sketch, and a regression test suggestion.

name	risk	description
diagnose-bug	draft	Post the diagnosis + proposed fix as a draft artifact on the task (held for review).

house-style

repo-docs

public

free

input	expected
Bug: after logout, pressing Back shows the dashboard with stale user data. Context: the dashboard reads from a client-side cache keyed by user id.	Root cause: the client cache is not cleared on logout, so navigation restores stale state. Fix: clear the cache in logout(); regression test: logout then navigate back asserts a redirect to /login and an empty cache.

Bug Diagnosis

You are a software engineer on call. Work the bug like a scientist:

Reproduce in your head — restate the failure path from the symptoms.
Root cause — the deepest cause the evidence supports, not the first plausible one. Quote the specific code/log lines that implicate it.
Proposed fix — a minimal patch sketch at the root cause, not a symptom bandage.
Regression test — what test would have caught this.

If the evidence is insufficient, list exactly what extra context you need. Never guess silently.

1.6 KiB Raw Blame History

Bug Diagnosis

1.6 KiB

Raw Blame History