Shared Flow Stories
===================

Flow Stories in this section are **cross-cutting** — they apply to every
agent created by ubFlow, not just ubFlow itself.

Need ID Display
---------------

.. flowstory:: Full need ID display with source links
   :id: FLST_UBFLOW_035
   :status: draft
   :tags: ubflow

   As a developer, I want every need ID referenced in any agent's output to
   be displayed in full and, where available, rendered as a link to its RST
   source file and line number, so that I can navigate directly to the
   definition of any rule or requirement without manual searching.

.. flowstory:: Reference driving instruction or skill in every decision
   :id: FLST_UBFLOW_037
   :status: draft
   :tags: ubflow

   As a **developer**, I want the ubFlow agent to reference the ``FLIN_`` or
   ``FLSK_`` that drives each decision it makes, so that I can trace every
   agent behavior back to its documented specification.

.. flowstory:: Mark undocumented decisions with NO FLOW
   :id: FLST_UBFLOW_038
   :status: draft
   :tags: ubflow

   As a **developer**, I want meaningful decisions that are not driven by any
   ``FLIN_`` or ``FLSK_`` to be explicitly marked ``NO FLOW``, so that gaps
   in the instruction set are visible at a glance and can be addressed.
   Formatting and phrasing choices shall be exempt and not reported.


Always-Load Rules
-----------------

.. flowstory:: Guarantee critical rules survive MCP bootstrap failure
   :id: FLST_UBFLOW_039
   :status: draft
   :tags: ubflow

   As a **developer**, I want critical agent instructions and skills to remain
   active even when the ubCode MCP bootstrap has not yet run or has failed,
   so that the most important behavioral rules are never silently absent from
   a session.


RST Authoring
-------------

.. flowstory:: Write all agent documentation content in valid RST syntax
   :id: FLST_UBFLOW_040
   :status: draft
   :tags: ubflow

   As a **developer**, I want all content the ubFlow agent writes into
   Sphinx-Needs RST files — including diagrams, code samples, tables, and
   notes — to use correct RST and Sphinx directive syntax so that every
   Sphinx build passes without warnings.


Agent Naming
------------

.. flowstory:: Give every agent a meaningful name instead of a number
   :id: FLST_UBFLOW_041
   :status: draft
   :tags: ubflow

   As a **developer**, I want agent IDs to carry a meaningful name segment
   rather than a sequential number so that any agent ID is self-descriptive
   and I can immediately understand which agent it refers to without looking
   it up.