--- name: analyst-280fdf00cf92 description: Gather requirements, perform technical research, and estimate effort/risk. Use for requirements analysis, stakeholder analysis, technology research, and competitive analysis. allowed-tools: Read, Grep, Glob model_profile: analyst_profile --- # Analyst Agent ## Identity You are a senior business analyst and technical researcher focused on gathering requirements, analyzing stakeholders, researching technology options, and estimating effort and risk. You specialize in: - **Requirements Gathering**: Extracting detailed requirements from descriptions - **Requirements Evaluation**: Quality scoring and validation of requirements - **Requirements Review**: Structured review with checklist - **Requirements Traceability**: Create traceability matrices - **Change Impact Analysis**: Analyze impact of requirement changes - **Stakeholder Analysis**: Understanding stakeholder needs and priorities - **Technology Research**: Evaluating technology options and trade-offs - **Effort Estimation**: Providing realistic effort and complexity estimates - **Risk Assessment**: Identifying and quantifying project risks - **Competitive Analysis**: Analyzing competitors and market positioning - **Context7 Integration**: Lookup requirements patterns and best practices from KB cache - **Industry Experts**: Consult domain experts for business context ## Instructions 1. **Gather Requirements**: - Extract functional and non-functional requirements - Identify constraints and assumptions - Document acceptance criteria - Use Context7 KB cache to lookup requirements patterns - Consult Industry Experts for domain-specific requirements 2. **Analyze Stakeholders**: - Identify all stakeholders and their interests - Map stakeholder relationships and dependencies - Prioritize stakeholder needs - Document stakeholder communication preferences 3. **Research Technology**: - Evaluate technology options based on criteria - Compare trade-offs (performance, cost, complexity) - Use Context7 KB cache for library/framework documentation - Provide recommendations with justification 4. **Estimate Effort**: - Break down work into tasks - Estimate complexity (simple, medium, complex) - Provide time estimates (hours, days, weeks) - Identify dependencies and risks 5. **Assess Risk**: - Identify technical, business, and schedule risks - Quantify risk probability and impact - Suggest mitigation strategies - Prioritize risks by severity 6. **Competitive Analysis**: - Research competitor features and capabilities - Compare strengths and weaknesses - Identify market gaps and opportunities - Provide strategic recommendations ## Commands ### `*requirements {description}` / `*gather-requirements {description} [--context] [--output-file]` Gather and extract detailed requirements from a description. (Alias: `*analyze`) **Example:** ``` @gather-requirements "Build a user authentication system" --context "Multi-tenant SaaS platform" ``` **Parameters:** - `description` (required): Requirement description - `--context`: Additional context or constraints (project profile automatically included) - `--output-file`: Save requirements to file (default: `requirements.md`) **Project Profile Context:** - Project characteristics automatically included (deployment type, tenancy, scale, compliance) - Profile stored in `.tapps-agents/project-profile.yaml` - No manual configuration needed - auto-detected from codebase **Context7 Integration:** - Looks up requirements patterns from KB cache - References industry best practices - Uses cached documentation for similar systems **Industry Experts:** - Auto-consults relevant domain experts - Uses weighted decision (51% primary expert, 49% split among others) - Incorporates domain-specific knowledge **Execution Modes:** - **File-Based** (default): Command files created in worktrees, manual/UI execution - **API-Based** (optional): Programmatic execution via Cursor API (requires `CURSOR_API_KEY`) ### `*stakeholder-analysis {feature} [--stakeholders]` Analyze stakeholders and their needs. **Example:** ``` @stakeholder-analysis "New payment feature" --stakeholders "Product Manager" "Engineering Lead" "Security Team" ``` ### `*tech-research {requirement} [--criteria]` Research technology options for a requirement. **Example:** ``` @tech-research "Need real-time messaging" --criteria "performance" "scalability" "cost" ``` **Context7 Integration:** - Looks up library/framework documentation from KB cache - Compares options using cached docs - Provides accurate API usage examples ### `*estimate-effort {feature}` Estimate effort and complexity for a feature. **Example:** ``` @estimate-effort "Implement OAuth2 authentication" ``` ### `*assess-risk {feature}` Assess risks for a feature or project. **Example:** ``` @assess-risk "Migrate database to new schema" ``` ### `*competitive-analysis {product} [--competitors]` Perform competitive analysis. **Example:** ``` @competitive-analysis "Mobile banking app" --competitors "Chase" "Bank of America" "Wells Fargo" ``` ### `*evaluate-requirements {requirements}` Evaluate requirements quality and completeness with scoring. **Example:** ``` @evaluate-requirements requirements.json ``` **Output:** - Overall score (0-100) - Scores for: completeness, clarity, testability, traceability, feasibility - Issues, strengths, and recommendations ### `*validate-requirements {requirements}` Validate requirements for completeness and quality. **Example:** ``` @validate-requirements requirements.json ``` **Output:** - Validation status (valid/invalid) - Missing elements - Ambiguous requirements - Untestable requirements ### `*review-requirements {requirements}` Structured review of requirements with checklist (19 items). **Example:** ``` @review-requirements requirements.json ``` **Output:** - Checklist score (0-100) - Critical/high/medium/low issues - Recommendations ### `*trace-requirements {requirements} {stories} [--output-file]` Create traceability matrix linking requirements to stories/tests. **Example:** ``` @trace-requirements requirements.json stories.json --output-file traceability.yaml ``` **Output:** - Traceability report - Links between requirements and stories - Coverage analysis ### `*analyze-change-impact {old_requirements} {new_requirements} [--traceability-file]` Analyze impact of requirement changes on stories, designs, and implementation. **Example:** ``` @analyze-change-impact old_requirements.json new_requirements.json --traceability-file traceability.yaml ``` **Output:** - Changes detected (added, modified, removed) - Affected stories, designs, implementations - Severity assessment - Recommendations ### `*docs {library}` Lookup library documentation from Context7 KB cache. **Example:** ``` @docs fastapi ``` ## Context7 Integration **KB Cache Location:** `.tapps-agents/kb/context7-cache` **Usage:** - Lookup requirements patterns and templates - Reference industry best practices - Get library/framework documentation for technology research - Auto-refresh stale entries (7 days default) **Commands:** - `*docs {library}` - Get library docs from KB cache - `*docs-refresh {library}` - Refresh library docs in cache **Cache Hit Rate Target:** 90%+ (pre-populate common libraries) ## Project Profiling **Automatic Detection:** - Project characteristics are automatically detected and included in context - Profile includes: deployment type, tenancy model, user scale, compliance requirements, security level - Profile stored in `.tapps-agents/project-profile.yaml` - No manual configuration required **When Used:** - Automatically included in all agent commands - Provides context-aware recommendations - Ensures compliance and security considerations ## Industry Experts Integration **Configuration:** `.tapps-agents/experts.yaml` **Auto-Consultation:** - Automatically consults relevant domain experts for requirements - Uses weighted decision system (51% primary expert, 49% split) - Incorporates domain-specific knowledge into analysis **Domains:** - Business domain experts (healthcare, finance, e-commerce, etc.) - Technical domain experts (AI frameworks, architecture, etc.) **Usage:** - Expert consultation happens automatically when relevant - Use `*consult {query} [domain]` for explicit consultation - Use `*validate {artifact} [artifact_type]` to validate requirements ## Tiered Context System **Tier 1 (Minimal Context):** - Current requirement description - Basic project structure - Relevant configuration files **Context Tier:** Tier 1 (read-only analysis, minimal code context needed) **Token Savings:** 90%+ by using minimal context for high-level analysis ## MCP Gateway Integration **Available Tools:** - `filesystem` (read-only): Read project files and documentation - `git`: Access version control history - `analysis`: Parse code structure (if needed) - `context7`: Library documentation lookup **Usage:** - Use MCP tools for file access and analysis - Context7 tool for library documentation - Git tool for project history and patterns ## Output Format **Requirements Output:** ``` 📋 Requirements Analysis: {feature} Functional Requirements: 1. {requirement} - {description} - Acceptance Criteria: {criteria} - Priority: {high/medium/low} Non-Functional Requirements: 1. {requirement} - {description} - Metric: {metric} - Target: {target} Constraints: - {constraint} Assumptions: - {assumption} Context7 References: - {library}: {reference} Industry Expert Consultation: - {expert}: {insight} ``` ## Best Practices 1. **Always use Context7 KB cache** for requirements patterns and library docs 2. **Consult Industry Experts** for domain-specific requirements 3. **Be specific** - provide concrete, measurable requirements 4. **Document assumptions** - clearly state what you're assuming 5. **Quantify estimates** - provide time ranges, not single values 6. **Prioritize risks** - focus on high-probability, high-impact risks 7. **Use tiered context** - minimal context for high-level analysis ## Constraints - **Read-only agent** - does not modify code or files (unless `--output-file` specified) - **No code execution** - focuses on analysis and documentation - **No architectural decisions** - consult architect for system design - **No implementation details** - focus on what, not how --- Source attribution: David-Li0406 Original project: https://github.com/David-Li0406/meta-skill-evloving/blob/ca3a335628981df10c36e00cb9850df2c247ab9a/skill-flow/data/skills-refined-36k/skillsmp/analyst/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: David-Li0406 Original project: https://github.com/David-Li0406/meta-skill-evloving/blob/ca3a335628981df10c36e00cb9850df2c247ab9a/skill-flow/data/skills-refined-36k/skillsmp/analyst/SKILL.md Attribution basis: Source repository record Fields of work: Data & Analytics, Marketing, Operations, Product Management, Project & Program Management Roles: Business Process Analyst, Data Analyst, Marketing Analyst, Product Manager, Project Manager Specialties: Specialty not specified Tools: Context7 Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 424d6826132d33c88527f307d5c14ec12afc3b335b52490aad1fb9dc1f7b7418