codex-astra-uxlisted
Install: claude install-skill thientranhung/astragentic
# Journeys before implementation
Read the existing PRD, glossary and owner notes. Reuse actor names and journey IDs;
do not replace an established vocabulary. Ask for the owner's current picture first.
Work through who acts, what triggers the journey, what they see/do, the successful
outcome, failure/recovery and permissions. Research facts from the project; route
product choices to the owner. Ask focused questions with available Codex tools or
plain text; never invent a question tool or infer an unanswered decision.
Draft journeys as UJ-n with actor, trigger, steps and observable outcome. Keep glossary,
requirements, non-goals and open questions alongside them in the existing PRD structure.
Show changed meaning for owner review. Write only within the task's document authority;
a BA with read-only scope returns proposed text instead of modifying the project.
Preserve prior IDs and decisions. Stop when the scoped journeys and open decisions are
explicit, not when an arbitrary number of interview rounds has passed.
Hand back PRD path/revision, journey IDs and unresolved decisions to the shaping owner.
A backend-only effort may use existing actors/contracts without inventing screens.