ڠjhSrSSKJr SSKJrJr SSKJr SSKJ r SSK J r J r SSK Jr SSKJrJr "S S 5rS S jrg )zRequirement Analyst skill.) annotations)ListOptional)RequirementsArtifact) JiraIssue) LLMClientget_llm_client sanitize_text) KnowledgeHitKnowledgeServicec:\rSrSrSSSjjrSSjrSrg) RequirementAnalystNcdU=(d [5UlU=(d [5Ulg)N)r llmr knowledge)selfrrs ;/var/www/html/gaurav/packages/agents/requirement_analyst.py__init__RequirementAnalyst.__init__s# *.*"8&6&8cP# URSUR3nURRUSS9IShvN n[ X5nUR R U5IShvN nURUlUR(dURUlUR(dn[UR5S:aUUR=(d SS:a<UR(a+SUl /UlUR=(d SS -UlU$NN7f) N )limitrgffffff?Tz9 | Auto-cleared after human comments (non-blocking gaps).)summary descriptionrgatherbuild_analyst_promptranalyze_requirementskeyjira_keyis_clearlenacceptance_criteria confidencecommentsclarification_questionsnotes)rissuequeryhitspromptartifacts ranalyzeRequirementAnalyst.analyzes==/5#4#4"56^^**5*::%e266v>>!II$}}H !!H001Q6$$)c1 $H /1H ,&nn26qqHN#;>s"9D&D"-D&)D$*B9D&$D&)rr)NN)rzOptional[LLMClient]rzOptional[KnowledgeService]returnNone)r-rr4r)__name__ __module__ __qualname____firstlineno__rr2__static_attributes__rrrrs0$(049 9.9  9rrcUR=(d /nSRSURSS55nSRSUR55=(d SnUVs/sHoURS:XdMUPM nnUVs/sHoURS:XdMUPM nnSS jnS UR S [ UR5S URS SRUR5S[ UR5SU(a![S5RSU55OSSU=(d SSUSU"U5SU"U5S3$s snfs snf)N c 3# UHFnSURS5S[[URS5=(d S553v MH g7f)- author: bodyrN)getr str).0cs r 'build_analyst_prompt../sBSga"QUU8_ R c!%%-2E2.F GHISgsA Aiz, c3# UH6oRS5=(d URS5=(d Sv M8 g7f)filenameid?N)rCrEas rrGrH2s._M^EE*-CtCCM^s=?(none) confluencegitcBU(dgSRSU55$)NrOr=c3X# UH!nSURSUR3v M# g7f)r?rAN)titlesnippet)rEhs rrG4build_analyst_prompt..fmt..9s%Ab2aggYb 4bs(*)join)hss rfmt!build_analyst_prompt..fmt6syyAbAAAruYou are the Requirement Analyst for Agent Nova (Salesforce development automation). Decide if the Jira requirement is clear enough to implement allowlisted Salesforce metadata. Clarity rules (follow strictly): - Set is_clear=true when the story identifies the target object, what metadata to create/change, and the expected behavior — OR has explicit acceptance criteria covering those. - Prefer reasonable defaults over questions for minor scope details (which layouts, record types, profiles, naming style, docs/training). - Only set is_clear=false for true blockers: missing object, no concrete change, no behavior/AC, or conflicting requirements. - If Comments contain human answers, treat them as locked decisions. Do not re-ask the same or equivalent questions; set is_clear=true unless a real blocker remains. - Never invent acceptance criteria that are not present or clearly stated in comments. - When is_clear=true, clarification_questions MUST be an empty list. Jira key: z Summary: z Status: z Labels: z Description: z Acceptance criteria: c3<# UHnS[U5-v M g7f)r?Nr rMs rrGrHOs 2r!d]1%%rsu7(none provided — extract from Description if present)z Comments: z Attachments: z Confluence hits: z Repository hits: z v1 allowlist: custom fields, validation rules, record-triggered Flows, Apex classes/triggers, LWCs, permission sets. Out of scope: production deploy, merge, sharing/OWD redesign, destructive deletes. )rYList[KnowledgeHit]r4rD) r(rXr* attachmentssourcer$r rstatuslabelsr chr) r-r/acr*r_rV conf_hits repo_hitsrZs rr"r"-s{  " " (bByySXSaSabebfSgH))_UM^M^__kckK =DqHH $<DI= 6DqHH$5DI6B   99+  & '(  5<< !"u  !"#79R 2r 22>wxy X]YY?# #>6s*E E  E%"E%N)r-rr/r^r4rD)__doc__ __future__rtypingrrpackages.artifacts.requirementsrpackages.integrations.jirarpackages.integrations.llmrr packages.integrations.sanitizer packages.knowledge.retrieversr r rr"r;rrros, "!@0?8H>1r