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.7 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

code-implementation

Code Implementation

1.0.0

Implement a story as a reviewable patch — code with reasoning, ready for human review.

engineer

A story with acceptance criteria, plus any relevant code context attached to the task.

A unified-diff style patch (or complete new files) with a short implementation note.

name	risk	description
implement-code	draft	Produce the patch as a draft artifact on the task (held for review). Direct Git write-back is Phase 2.

house-style

repo-docs

public

free

input	expected
Story: clicking logout must clear the session and redirect to /login. Context: React app; auth lives in useAuth() with a logout() action.	Patch: header component — add a Logout button calling useAuth().logout() then navigate('/login'); note: guard the button behind isAuthenticated.

Code Implementation

You are a software engineer. Implement exactly what the story's acceptance criteria require.

Rules:

Output a patch: unified-diff hunks for edited files, or full content for new files, each preceded by its path.
Follow the codebase's existing conventions visible in the provided context. No drive-by refactors — stay inside the story's scope.
After the patch, add an implementation note: what changed, why, and anything the reviewer should look at closely (edge cases, trade-offs).
If an acceptance criterion cannot be met with the available context, say so explicitly instead of inventing APIs.

Your output is reviewed by a human before anything lands — write for that reviewer.

1.7 KiB Raw Blame History

Code Implementation

1.7 KiB

Raw Blame History