plan-search

Create investigation checklists and gather requirements from JIRA and Slack.

Updated Jul 8, 2017
One-click install
npx skills add https://github.com/mczkzk/dotfiles --skill plan-search
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-search
Source: https://github.com/mczkzk/dotfiles/tree/main/dot_claude/skills/plan-search
Command: npx skills add https://github.com/mczkzk/dotfiles --skill plan-search

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the initial investigation and requirement gathering phase for new features, ensuring all necessary information is collected before detailed planning begins.

Core Features & Use Cases

  • Automated JIRA Fetching: Automatically retrieves ticket details for task IDs.
  • Slack Discussion Search: Gathers context from relevant Slack conversations.
  • Interactive Checklist: Guides users through a comprehensive investigation checklist covering code, database, and external dependencies.
  • Use Case: Before starting development on a new user authentication feature, use this Skill to automatically pull JIRA ticket details, find related Slack discussions, and then systematically go through a checklist to ensure all technical aspects are understood.

Quick Start

Use the plan-search skill to create an investigation checklist for the user-auth feature.

Frequently Asked Questions about plan-search

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate JIRA ticket fetching and Slack context gathering for feature planning?

Automating feature planning fetches JIRA ticket details and searches Slack discussions using a given task ID or feature name. This automatically aggregates project context to inform the initial investigation phase.

What is included in a feature development investigation checklist?

A feature development investigation checklist comprehensively analyzes the codebase, database schemas, external dependencies, and testing strategies. It systematically ensures all technical aspects are understood before detailed planning begins.

How do I gather requirements for a new feature before starting development?

Gathering requirements for a new feature involves automatically retrieving JIRA issue details and searching relevant Slack conversations. It then guides you through an interactive checklist to ensure all technical dependencies are identified.

Does this automated investigation checklist work with both a feature name and a JIRA task ID?

Yes, the automated investigation checklist accepts either a descriptive feature name or a specific JIRA task ID as input. It uses whichever identifier is provided to fetch relevant issue details and contextual discussions.

What's the best way to investigate external dependencies and codebase impact for a new feature?

The best way to investigate external dependencies and codebase impact is using an automated interactive checklist. It systematically walks through potential effects on databases and external services before you proceed to detailed planning.

Can I use Slack discussion search to inform my technical planning process?

Yes, Slack discussion search gathers relevant conversation context to inform the technical planning process. It automatically retrieves related discussions to ensure comprehensive analysis of codebase and external dependencies.