skills.rest
danzam98
danzam98COMMUNITY
Explore all skills by this author →
GitHub

system-weaknesses

Identify and document system weaknesses across architecture, workflows, and tooling.

1|Updated Feb 9, 2026
Search Tags:#ideation#refactor#improvement#analyze#weaknesses#risk#system
One-click install
npx skills add https://github.com/danzam98/claude-skills-toolkit --skill system-weaknesses
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: system-weaknesses
Source: https://github.com/danzam98/claude-skills-toolkit/tree/main/skills/system-weaknesses
Command: npx skills add https://github.com/danzam98/claude-skills-toolkit --skill system-weaknesses

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and document the weakest parts of the system that require fresh ideas and improvements.

Core Features & Use Cases

  • Identify weaknesses across architecture, workflows, and tooling.
  • Generate actionable improvement ideas and refactoring prompts.
  • Use case: after a thorough session, surface top improvement opportunities to guide planning and execution.

Quick Start

Provide a prioritized list of system weaknesses and actionable improvement ideas.

Frequently Asked Questions about system-weaknesses

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

FAQPage Schema
How do I identify system weaknesses for architecture and workflow improvements?▼

To identify system weaknesses, apply this analysis after thoroughly exploring your system to surface prioritized improvement opportunities across architecture, processes, and tooling. It outputs actionable refactoring recommendations and structured ideation prompts.

What is the best way to generate actionable refactoring ideas after a system exploration session?▼

Generating actionable refactoring ideas requires documenting the weakest system parts that need fresh improvements. This approach provides a prioritized list of weaknesses and structured ideation prompts to guide planning and execution.

Can I use this to analyze risks across both architecture and tooling simultaneously?▼

Yes, you can analyze risks across architecture and tooling simultaneously. It identifies and documents weaknesses across workflows, processes, and system structures to surface top improvement opportunities for comprehensive risk analysis.

When do I need to document system weaknesses for structured ideation?▼

You need to document system weaknesses for structured ideation when you require fresh ideas and prioritized improvements. Apply this after a thorough exploration session to guide planning and execution with actionable recommendations.

Does analyzing system weaknesses require any specific tooling dependencies?▼

Analyzing system weaknesses requires no specific tooling dependencies. It operates independently to document vulnerabilities and generate prioritized improvement ideas across your architecture, workflows, and existing tooling environment.

Why does my system analysis fail to produce actionable improvement ideas?▼

Your system analysis fails to produce actionable improvement ideas if it is not applied after a thorough exploration of the system. Structured ideation requires documented weaknesses across architecture and processes to generate prioritized refactoring recommendations.

Related Skills

Explore More Software Engineering Skills→
attunehqattunehq
1

codebase-documenter

Generate markdown documentation detailing architecture, components, data flow, and development guidelines.

Official
Advanced
WizarckWizarck

qa-improve

Analyze GTM-Helper AI architecture and propose prioritized preventive improvements.

Community
Advanced
wangrenzhu-olawangrenzhu-ola
2

gh:ideate

Generate and evaluate grounded improvement ideas for the current codebase.

Community
Advanced
saschadudkin-sketchsaschadudkin-sketch

security-reviewer

Identify security vulnerabilities in code and infrastructure and generate audit reports with severity ratings.

Community
Advanced