foresee

Analyze software artifacts to identify medium-term issues and risks.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/RebelliousSmile/my-claude-marketplace --skill foresee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foresee
Source: https://github.com/RebelliousSmile/my-claude-marketplace/tree/main/plugins/overcode/skills/foresee
Command: npx skills add https://github.com/RebelliousSmile/my-claude-marketplace --skill foresee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill conducts prospective analysis of your documents, code, and dependencies to uncover medium-term issues and risks that tests and linters miss.

Core Features & Use Cases

  • Prospective Analysis: Analyze documents, code, and dependencies for potential future issues and risks.
  • Scorecard: Generate a scorecard with scores for three action-specific dimensions and a list of improvements.
  • Use Case: Use this Skill to analyze your project's architecture before significant changes, ensuring future maintainability and performance.

Quick Start

Run the foresee skill on your codebase with '/foresee src/'.

Frequently Asked Questions about foresee

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

FAQPage Schema
How do I analyze code for future maintainability risks before major changes?

To analyze code for future maintainability risks, run prospective analysis on your software artifacts to identify medium-term issues and architectural risks that standard tests and linters miss. Use '/foresee src/' to scan your codebase and generate a scorecard with actionable improvements.

What is prospective analysis for software engineering?

Prospective analysis is the process of evaluating documents, code, and dependencies to uncover future issues and risks. It generates a scorecard with scores across action-specific dimensions and a list of improvements for project planning and risk assessment.

Do I need Python libraries to run dependency analysis on my project?

Yes, you need Python libraries to run dependency analysis. The Skill requires these libraries to parse and analyze software artifacts for prospective analysis and risk identification.

Does prospective analysis find issues that linters and tests miss?

Yes, prospective analysis finds issues that linters and tests miss. It evaluates software artifacts to identify medium-term architectural risks and future maintainability issues rather than immediate syntax or functional errors.

How do I generate a scorecard for code quality and dependency risks?

Generate a scorecard for code quality and dependency risks by running the Skill on your project directory. It outputs scores for three action-specific dimensions and a list of improvements.