architectural-analysis
openbooklet.com/s/architectural-analysisopenbooklet.com/s/architectural-analysis@1.0.0GET /api/v1/skills/architectural-analysisPerforms deep architectural analysis of a specified module, directory, or feature area by examining structural coupling, data flow, concurrency patterns, risk, and SOLID alignment. Use when the user wants to assess, evaluate, or review the architecture, design quality, dependency structure, coupling, cohesion, or technical debt of an existing part of the codebase â including requests to audit module boundaries, check for architectural smells, or inform refactoring decisions. Requires a specific focus area (module, directory, or component) to analyze. Not for creating new project structures, scaffolding, or boilerplates. Not for investigating specific bugs, runtime errors, or failures â use investigate. Not for test planning â use test-planning. Not for file-level code review â use code-review. Not for writing documentation or architectural decision records.
This skill runs a progressive-disclosure code overview with the core `han-coding:code-overview` skill, lets the user review the resulting overview, and then publishes it to a Confluence location that **the user must specify**. It is a thin orchestrator: the overview work belongs to `han-coding:code-
Capture structured feedback on the Han skills and agents used in the current session and optionally post it as a GitHub issue to testdouble/han. Use at the end of any session where one or more han-* skills or agents ran, to rate a run, log what worked and what didn't, or submit observations for maintainers. Does not review code, investigate bugs, or research options; use code-review, investigate, or research for those. Does not provide feedback on skills or agents from non-Han plugins.
Convert a stakeholder summary markdown file into a single self-contained HTML report tailored for executive readers â bottom line and decision asks up front, supporting detail later â styled with a Test Double-derived palette. The skill produces one HTML file next to the source markdown and stop
This skill runs an evidence-based investigation with the core `han-coding:investigate` skill, lets the user review the resulting report, and then publishes it to a Confluence location that **the user must specify**. It is a thin orchestrator: the investigation work belongs to `han-coding:investigate
This skill takes one local Markdown file and publishes it to a Confluence location that **the user must specify** â creating a new page or updating an existing one through the Atlassian MCP server. It owns everything about the posting itself: the MCP preflight, resolving the destination, reading t
This skill builds a feature specification with the core `han-planning:plan-a-feature` skill, lets the user review the result, and then publishes it to a Confluence location that **the user must specify**. It is a thin orchestrator: the planning work belongs to `han-planning:plan-a-feature`, and the
Break an implementation plan into vertical slices (tracer bullets) and write them as work items to a single `work-items.md` file.
This skill produces project documentation with the core `han.core:project-documentation` skill, lets the user review the result, and then publishes it to a Confluence location that **the user must specify**. It is a thin orchestrator: the documentation work belongs to `han.core:project-documentation
Take an already-broken-down `work-items.md` file (produced by `/plan-work-items`) and publish each slice as a GitHub issue in its target repo.
Take an already-broken-down `work-items.md` file (produced by `/plan-work-items`) and publish each slice as a Jira ticket in a single target project.
Auto-indexed from testdouble/han
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.