Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    business analysis planner

    1

    Business analysis often stalls before it starts because teams jump straight into requirements without a plan.

    $10

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    business analysis planner

    business analysis planner

    Example session with this skill installed

    Plan the analysis for a new automated employee onboarding system. The sponsor is the HR Director. We use Jira and have 3 weeks for elicitation. Stakeholders include HR, IT, and new hires.

    • Read your context and instructions
    • Compiled the business analysis planner

    I have developed the business analysis plan for the automated employee onboarding system initiative.

    Business Analysis Plan — Automated Employee Onboarding System, 2024-05-20

    1. Initiative framing, sources and assumptions

    • Source E1: User prompt regarding HR Director sponsorship and 3-week timeline.
    • Assumption: IT infrastructure is available to support a new automated tool.

    2. Business need and scope

    The HR Department has a manual onboarding process that takes 15 hours per hire, resulting in delayed equipment access and low new-hire satisfaction, as evidenced by the 2023 Pulse Survey.

    Analysis difficulty: Medium — Multiple stakeholder groups and integration with existing IT systems.

    OutcomeMeasureBaselineTargetEvidence
    Reduced manual effortHours per hire15h4hHR Time Logs
    Faster tool accessDays to access5 days0 daysIT Ticket Logs

    3. Stakeholders and involvement

    GroupImpactEffectKnowledgeStanceInvolvement
    HR StaffHighHighCurrent processSupportiveCo-design
    IT OpsHighMediumIntegrationsNeutralCo-design
    New HiresLowHighUser experienceUnknownConsult

    4. Elicitation plan

    #Stakeholder groupInformation neededTechniqueWhyEffort (h)
    1HR StaffProcess stepsWorkshopHigh collaboration12
    2IT OpsTechnical specsInterviewTechnical depth6
    3New HiresPain pointsSurveyBroad reach4

    Analytical estimate — validation required

    5. Requirement types and traceability

    Traceability depth: Standard.

    • Type: Business Requirement (BR), Kept: Yes, Linked to: Stakeholder Need.
    • Type: Functional Requirement (FR), Kept: Yes, Linked to: BR.

    8. Risks to the analysis

    #Risk to the analysisLikelihoodImpactEarly warningResponse
    1Stakeholder unavailabilityHighHighDeclined invitesEscalate to HR Director
    2Scope creepMediumHighNew tool requestsRe-align to need statement

    Next steps

    1. Review the elicitation effort estimates with the project team.
    2. Confirm the Management decision required for the prioritization tie-break order.
    3. Schedule the initial process workshop with HR staff.

    This plan supports, and does not replace, the business analyst's professional judgment and the sponsor's decisions.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Business analysis often stalls before it starts because teams jump straight into requirements without a plan. This skill transforms a brief initiative description into a structured roadmap for the analysis phase, ensuring you identify the right stakeholders and elicitation methods before a single user story is written.

    What it does

    • Initiative Framing creates a clear need statement that separates the core problem from proposed solutions.
    • Stakeholder Mapping identifies groups, their observed stance, and the required involvement level.
    • Elicitation Planning selects specific techniques like workshops or prototyping based on information needs and stakeholder impact.
    • Traceability Setup defines requirement types, ID prefixes, and the depth of links needed for the project scale.
    • Risk Assessment identifies 5 to 8 specific risks to the analysis process itself with early-warning signs.

    How it works

    1. Intake where you provide an initiative description, sponsor details, and any known constraints.
    2. Analysis Difficulty Assessment where the tool classifies the work as Low, Medium, or High difficulty.
    3. Plan Generation producing a structured Markdown document covering scope, stakeholders, techniques, and sign-off paths.
    4. Validation where you review analytical estimates and flag management decisions for the sponsor.

    Frameworks & tools

    This skill follows standard business analysis practices compatible with BABOK and PMI standards. It produces GitHub-flavored Markdown suitable for project wikis, Jira, or Azure DevOps.

    Why this beats prompting it yourself

    Generic prompts often produce a list of requirements instead of a plan for how to get them. This skill enforces a rigorous methodology that separates documented facts from analytical estimates and forces a clear traceability and validation strategy.

    Use cases

    • Drafting a business analysis approach for a new system replacement or process change.
    • Creating an elicitation schedule with effort estimates for a project kickoff.
    • Setting up a requirements management plan including MoSCoW prioritisation rules.
    • Identifying gaps in an existing analysis strategy before committing resources.

    Known limitations

    Does not write the actual requirements, user stories, or process models. It does not provide project budgets or legal rulings.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Business & Operations.

    Does not generate requirements, user stories, or code. Excludes project scheduling, budgeting, and legal/compliance advice. Requires a description of the initiative to function.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    Permissions

    No special permissions declared or detected

    Listed5 days ago

    What's inside

    Frequently Asked Questions

    This skill provides the strategic roadmap for the analysis phase—including stakeholder maps and elicitation schedules—rather than writing the end-state user stories or functional requirements themselves.

    The output is generated in GitHub-flavored Markdown, making it easy to copy and paste directly into project wikis, Jira descriptions, Confluence pages, or Azure DevOps documentation.

    No complex setup is required; once you provide your initiative's description and sponsor details, the skill automatically classifies the project difficulty and generates the structured plan.

    Yes, the generated plan is built to be compatible with BABOK and PMI standards, ensuring your analysis strategy meets professional industry benchmarks.

    You receive full access to the Business Analysis Planner skill, including the difficulty assessment logic, stakeholder mapping module, and risk assessment templates.

    New in Business & Operations