skills.rest
grigb
grigbCOMMUNITY
Explore all skills by this author →
Website𝕏@SpiritBitsGitHub

chief-reality-officer

Validate project plans and technical designs for feasibility risks and real-world constraints.

4|Updated Dec 7, 2025
Search Tags:#planning#strategy#feasibility#risk-assessment#project-management#reality-check
One-click install
npx skills add https://github.com/grigb/gas-prompt-library --skill chief-reality-officer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chief-reality-officer
Source: https://github.com/grigb/gas-prompt-library/tree/main/agents/agent-chief-reality-officer
Command: npx skills add https://github.com/grigb/gas-prompt-library --skill chief-reality-officer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents project failure by identifying hidden risks, validating assumptions, and pressure-testing feasibility before teams commit to over-engineered or unrealistic plans.

Core Features & Use Cases

  • Assumption Validation: Systematically extracts and tests both explicit and implicit project assumptions.
  • Risk Cataloging: Provides structured feasibility assessments, risk registers, and pragmatic alternatives to keep projects on track.
  • Use Case: Before launching a complex new feature, use this skill to audit the technical architecture and timeline, ensuring the plan accounts for real-world constraints like API limits and resource availability.

Quick Start

Invoke the chief-reality-officer skill to perform a feasibility audit on the current project plan and identify any high-impact risks.

Frequently Asked Questions about chief-reality-officer

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

FAQPage Schema
How do I validate project assumptions and assess feasibility risks before implementation?▼

Assess feasibility by systematically evaluating technical, resource, and timeline dependencies to identify hidden risks and ground ambitious plans in real-world constraints before team commitment.

When do I need a feasibility audit for technical architecture and project planning?▼

A feasibility audit is needed when pressure-testing project viability to prevent over-engineered plans, ensuring that technical architectures account for real-world constraints and hidden risks.

How do I identify hidden risks in a project plan to prevent failure?▼

Prevent project failure by pressure-testing feasibility through assumption validation, cataloging risks across business and engineering domains to expose constraints that threaten project viability.

Can I use risk assessment to generate pragmatic alternatives for over-engineered plans?▼

Generating pragmatic alternatives requires evaluating technical and timeline dependencies, allowing you to adjust over-engineered plans into viable, risk-adjusted project roadmaps across business domains.

Does feasibility risk assessment work for both business and engineering domains?▼

Risk assessment functions across business and engineering domains by systematically evaluating resource and technical dependencies, providing structured feasibility assessments that ground assumptions in real-world constraints.

Related Skills

Explore More Product & Management Skills→
sfc-gh-samaurersfc-gh-samaurer

sd-technical-deal-review

Generate structured technical deal review proposals for Snowflake projects.

Community
Intermediate
KurarionKurarion
72

create-plan

Generate validated Markdown implementation plans with objectives, tasks, and risks.

Community
Advanced
dralgorhythmdralgorhythm
111

agile-methodology

Automate agile ceremonies and backlog management for Scrum and Kanban teams.

Community
Intermediate
ljucaskljucask
1

pm-tech-feasibility

Generate structured technical feasibility reports from product requirements and engineering research.

Community
Advanced