analysis

Create structured analyses with numbered findings, execution plans, and task materialization

11 stars

Best use case

analysis is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Create structured analyses with numbered findings, execution plans, and task materialization

Teams using analysis should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/analysis/SKILL.md --create-dirs "https://raw.githubusercontent.com/hivellm/rulebook/main/.claude/skills/analysis/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/analysis/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How analysis Compares

Feature / AgentanalysisStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Create structured analyses with numbered findings, execution plans, and task materialization

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

Create a structured analysis for: $ARGUMENTS

Steps:
1. Call `rulebook_analysis_create` with the topic to scaffold `docs/analysis/<slug>/`
2. Check existing knowledge: `rulebook_knowledge_list` and `rulebook_memory_search` for prior context
3. Investigate the topic — read relevant files, search codebase, fetch docs as needed
4. Fill `findings.md` with numbered findings (F-001..F-NNN), each with: title, evidence (file:line), impact, confidence
5. Design phased execution plan in `execution-plan.md`
6. Consolidate the executive summary in `README.md`
7. Capture each key finding to the knowledge base: `rulebook_knowledge_add` for patterns/anti-patterns
8. Save analysis summary to memory: `rulebook_memory_save` with type `observation` and tags `["analysis", "<slug>"]`
9. Offer to materialize implementation tasks from the execution plan via `rulebook_task_create`