skills.rest
tachyon-beep
tachyon-beepCOMMUNITY
Explore all skills by this author →
GitHub

prioritizing-improvements

Enforce risk-based prioritization with a security-first Phase 1 roadmap.

1|Updated Oct 29, 2025
Search Tags:#documentation#roadmap#prioritization#stakeholders#risk-based#security-first
One-click install
npx skills add https://github.com/tachyon-beep/hamlet --skill prioritizing-improvements
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prioritizing-improvements
Source: https://github.com/tachyon-beep/hamlet/tree/main/.claude/skills/axiom-system-architect/skills/prioritizing-improvements
Command: npx skills add https://github.com/tachyon-beep/hamlet --skill prioritizing-improvements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces risk-based prioritization to keep security as the top priority when stakeholders push for non-security work.

Core Features & Use Cases

  • Risk-based prioritization ensures security remains Phase 1 non-negotiable.
  • Provides a structured, phase-based roadmap with explicit documentation of decisions and trade-offs.
  • Use cases include prioritization debates, technical debt remediation planning, and governance reviews where security risk must drive outcomes.

Quick Start

Use prioritizing-improvements to draft a Phase 1 security-first plan and a three-phase roadmap with explicit decision notes.

Frequently Asked Questions about prioritizing-improvements

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

FAQPage Schema
How do I keep security prioritized when stakeholders push for non-security features on the roadmap?▼

Risk-based prioritization keeps security prioritized under stakeholder pressure by enforcing a non-negotiable security phase before other work. It provides a structured, phase-based roadmap with explicit documentation of trade-offs to ensure security posture drives outcomes.

What is risk-based prioritization for technical debt remediation?▼

Risk-based prioritization for technical debt remediation is a structured method that enforces security risk as the primary driver for outcomes. It mandates a non-negotiable security phase before other work and requires explicit documentation of prioritization decisions.

How do I document roadmap decisions when security and stakeholder demands conflict?▼

Document roadmap decisions by applying a structured, phase-based approach that explicitly records trade-offs and prioritization debates. This ensures security risks drive governance reviews and technical debt remediation outcomes even under stakeholder pressure.

Does this approach require a separate security phase before approving other roadmap work?▼

Yes, this approach requires a non-negotiable Phase 1 security-first plan before other work begins. It enforces a structured three-phase roadmap with explicit decision notes to maintain security posture during stakeholder prioritization debates.

When do I need a security-first roadmap plan for governance reviews?▼

You need a security-first roadmap plan for governance reviews when stakeholder demands threaten your security posture. It enforces risk-based prioritization, ensures technical debt remediation follows a non-negotiable security phase, and documents decisions explicitly.

Related Skills

Explore More Product & Management Skills→
navapbcnavapbc
6

retro

Assess project health metrics and create a remediation plan with acceptance criteria.

Official
Advanced
cslsoftwarescslsoftwares

documentation-roadmap-from-docs

Generate a three-phase documentation roadmap from existing Documentation/ assets and hub artifacts.

Community
Advanced
WebWakaHubWebWakaHub
20

Sprint Prioritizer

Prioritize sprint backlogs using RICE, MoSCoW, Kano, and value versus effort scoring.

Official
Advanced
thecomputer07thecomputer07

qsd-list-phase-assumptions

Analyze a roadmap to surface phase assumptions across five areas.

Community
Intermediate