productivity

Stress-test proposals and resolve decision-tree branches through guided interviews.

2|Updated Feb 12, 2024

Search Tags:#planning #brainstorming #productivity #design review #stress-testing #decision-making #interviewing

Ready to run

npx skills add https://github.com/adibfirman/dotfiles --skill productivity-adibfirman

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: productivity
Source: https://github.com/adibfirman/dotfiles/tree/main/claude/.claude/skills/productivity
Command: npx skills add https://github.com/adibfirman/dotfiles --skill productivity-adibfirman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps convert vague plans and half-formed thoughts into a structured, decision-ready understanding by stress-testing proposals and improving personal workflow.

Core Features & Use Cases

Guided code-review routing: Breaks down whether an item belongs in a specific technical skill by using the user's review context as the decision driver.
Relentless design interrogation: Invokes a focused interview flow to resolve the decision tree until shared understanding is reached.
Use case: When you are proposing a system design or workflow and keep encountering uncertainty, it narrows the discussion to the next unanswered dependency or assumption.

Quick Start

Use the productivity skill to get planning and decision support by asking it to either route your request to the right technical skill or grill your design until all dependencies are resolved.

Frequently Asked Questions about productivity

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

FAQPage Schema

How do I stress-test a system design to resolve decision-tree dependencies?▼

Relentless design interrogation applies an interview flow to resolve decision-tree branches sequentially, ensuring shared understanding is reached before finalizing your system design.

What is the best way to route code review requests to the right technical skill?▼

Code review routing is handled by using your specific review context as the decision driver to determine whether an item belongs in a dedicated technical skill, breaking down the request to match the appropriate workflow.

How do I brainstorm and refine vague plans into decision-ready workflows?▼

Brainstorming vague plans into decision-ready workflows involves stress-testing proposals and driving clarification to shared understanding, effectively converting half-formed thoughts into structured personal workflow refinements.

Can I use this for design evaluation and interview-style interrogation of plans?▼

Yes, design evaluation and interview-style interrogation of plans are core features, invoking a focused flow that grills your design until all dependencies and assumptions are fully resolved.

When should I not use an interview-style interrogation approach for decision-making?▼

You should avoid interview-style interrogation for decision-making if your plan has no unresolved dependencies or assumptions, as the process specifically targets uncertainty by isolating unanswered decision-tree branches.