professional-agents

Use PROACTIVELY for code implementation, feature development, debugging, refactoring, and solving coding problems. MUST BE USED when asked to write code, implement features, or debug issues.

Use this agent when working with unpacked .doc or .docx files that need direct editing of content or formatting, or when retrieving specific information from the XML structure of unpacked Word documents. This agent specializes in manipulating the internal XML files (document.xml, styles.xml, settings.xml, etc.) that comprise Word documents rather than working with markdown conversions. Examples: - <example> Context: User needs to modify text formatting in a Word document while preserving all styling. user: "I need to change all instances of 'Phase 1' to 'Phase 2' in the document.xml file while keeping the bold formatting intact" assistant: "I'll use the docx-editor agent to handle this XML-level edit to ensure formatting preservation." <Task tool invocation to launch docx-editor agent> </example> - <example> Context: User wants to extract specific data from Word document structure. user: "Can you find all the custom properties stored in this unpacked docx file?" assistant: "I'm launching the docx-editor agent to parse the docProps files and extract the custom properties from the unpacked Word document structure." <Task tool invocation to launch docx-editor agent> </example> - <example> Context: User needs to modify document styles at the XML level. user: "I need to update the heading styles in this Word document to use a different font" assistant: "I'll use the docx-editor agent to directly edit the styles.xml file in the unpacked docx to modify the heading font specifications." <Task tool invocation to launch docx-editor agent> </example>

Use PROACTIVELY for user story analysis, requirements clarification, acceptance criteria review, feature prioritization, and stakeholder requirement translation. MUST BE USED when analyzing requirements or user stories.

Use PROACTIVELY for code quality review, security analysis, bug detection, and testing gap identification. MUST BE USED when reviewing existing code or analyzing code quality.

Use PROACTIVELY for technology research, competitive analysis, best practices investigation, security research, framework comparisons, and market analysis. MUST BE USED when asked to research, compare, investigate, or gather external information about technologies, trends, or solutions.

Use PROACTIVELY for project planning, timeline estimation, sprint planning, delivery risk assessment, stakeholder coordination, and resource allocation decisions. MUST BE USED when asked about project timelines, team capacity, or delivery planning.

Use PROACTIVELY for architecture decisions, technology stack selection, technical feasibility assessment, system design, and implementation planning. MUST BE USED when evaluating technical approaches or making architecture decisions.

Use PROACTIVELY for user interface design, user experience planning, wireframing, prototyping, design systems, accessibility review, and user journey mapping. MUST BE USED when asked about UI design, UX flows, user research, design patterns, or visual design decisions.