Transform rough product ideas into decision-complete implementation plans.
npx skills add https://github.com/redisread/product-stories --skill think-redisread
Please help me install this Agent Skill. Skill: think Source: https://github.com/redisread/product-stories/tree/main/.agents/skills/think Command: npx skills add https://github.com/redisread/product-stories --skill think-redisread
This Skill eliminates the costly cycle of jumping into implementation without validated planning, which leads to rework, missed constraints, and architectural debt. It ensures rough ideas are transformed into decision-complete plans with clear success criteria, constraints, and handoff steps before any code is written.
Use the think skill to evaluate whether the proposed real-time collaboration feature is worth building by running a value judgment assessment that considers commercial readiness, maintenance burden, and technical tradeoffs.
High-intent search queries and answers about installing and using this skill.
To validate rough product ideas before coding, transform them into decision-complete implementation plans using feasibility analysis and contradiction scanning. This process ensures chosen approaches, rejected tradeoffs, and verification steps are established upfront to prevent architectural debt and rework.
The best way to triage a multi-request feature bundle is to classify the incoming requests and apply quick fix recommendations for well-defined problems. This separates complex features requiring full architecture planning from lightweight fixes.
To evaluate whether a new feature is worth building, perform a value judgment assessment that analyzes commercial readiness, maintenance burden, and technical tradeoffs. This determines if the proposed feature passes market fit and feasibility gates before engineering begins.
Yes, you can use architecture planning to prevent rework on vague feature requests by converting them into structured implementation plans. This enforces durable context preflight checks and explicit rollback strategies before development starts.
When scanning for contradictions against project rules, limitations arise if the initial idea lacks enough context for durable preflight checks. The process requires explicit phase-independent handoff plans to function correctly and avoid missing architectural constraints.
toddwardTransform rough ideas into design proposals with structured questioning and alternatives.
burnjohnGenerate step-by-step implementation plans with explicit file paths and verifiable tasks.
Moonsong-LabsAutomate code review feedback processing with verification before implementation.
rjskeneClassify GitHub issues and apply pipeline triage labels.
