Engineering Blueprint
Interrogate Ideas Before Building
Force critical thinking on product assumptions before writing code
What problem does this solve?
Surfaces the real product hiding inside a vague feature request and challenges false premises before implementation. /office-hours conducts a six-question forcing interrogation (demand reality, status quo, specificity, narrowest wedge, observation, future-fit) to reframe what you are actually building. /spec turns the interrogation into a five-phase backlog-ready specification.
How does it work?
Run /office-hours first. Describe your idea naturally; the agent listens for pain points instead of feature requests, reframes the problem ("you said daily briefing but you are building a chief of staff AI"), challenges premises, and generates 2-3 implementation approaches with effort estimates. It writes a design doc that feeds into every downstream skill. Later, use /spec to convert a product idea into an executable specification (why, scope, technical details, draft, files) with a GitHub issue and optional agent spawn.
Key Features
/office-hours
Six forcing questions + premise validation + implementation alternatives with effort estimates. Design doc output feeds into all review skills.
/spec
Five-phase spec workflow (why, scope, read codebase, draft, file). Backlog-ready output with GitHub issue integration and optional Conductor agent spawn.
About This Blueprint
- Industry
- Technology
More Blueprints to explore
ICP-Filtered Outreach Lists from G2 Buyer Intent
Stop wasting rep time on weak intent signals and mismatched accounts. The workflow ranks ICP-fit buyers by readiness, finds the right contact, and supplies tailored outreach angles for the strongest opportunities.
Ishani D.
Account Manager at G2