elite-intent-architect-yashu

Clarify project requirements through progressive questioning and expert assumptions.

9|3|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/steelan9199/wechat-publisher --skill elite-intent-architect-yashu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: elite-intent-architect-yashu
Source: https://github.com/steelan9199/wechat-publisher/tree/main/skills/elite-intent-architect-yashu
Command: npx skills add https://github.com/steelan9199/wechat-publisher --skill elite-intent-architect-yashu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the issue of misaligned expectations and vague project requirements by forcing a structured, expert-led discovery process before any execution begins.

Core Features & Use Cases

  • Dynamic Progressive Questioning: Uses a structured, multi-turn approach to narrow down user intent without overwhelming them.
  • Expert Assumption Engine: Automatically fills in minor technical details based on industry best practices to reduce user cognitive load.
  • Use Case: When a user asks for a generic script, the skill identifies the core intent and constraints, ensuring the final output is tailored to the specific environment and performance needs.

Quick Start

Trigger the elite intent architect yashu skill by appending the keyword expert alignment to your request to begin the requirement clarification process.

Frequently Asked Questions about elite-intent-architect-yashu

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

FAQPage Schema
How do I transform vague project requirements into precise technical blueprints?

Transform vague project requirements into precise blueprints by employing dynamic progressive questioning and expert-driven assumptions to validate core parameters, ensuring task alignment before technical execution begins.

What is the best way to align ambiguous user intent with software development workflows?

Align ambiguous user intent with software development workflows by using a structured, expert-led discovery process that validates constraints through multi-turn questioning before initiating final code generation.

How does progressive questioning work for project scoping and requirement engineering?

Progressive questioning for project scoping works by using a structured, multi-turn approach to narrow down user intent dynamically without overwhelming them, bridging the gap between ambiguous requests and execution.

Do I need to provide all technical details for project scoping, or are assumptions made?

You do not need to provide all technical details for project scoping; an expert assumption engine automatically fills in minor technical details based on industry best practices to reduce cognitive load.

When should I use expert-driven decision support for requirement engineering?

Use expert-driven decision support for requirement engineering when facing misaligned expectations and vague project constraints, ensuring final outputs are tailored to specific environments before execution starts.

Can I use this for consulting workflows to bridge user intent and technical execution?

Yes, you can use this for consulting workflows to bridge user intent and technical execution, operating within professional software development environments to validate core parameters through structured decision-making.