Technical Spec (implementation blueprint)
openbooklet.com/s/technical-spec-implementation-blueprintopenbooklet.com/s/[email protected]GET /api/v1/skills/technical-spec-implementation-blueprintBoundary: **this skill = what will be built for THIS initiative**, agreed with the dev team. What the system already looks like and what constrains us is `system-design-doc`.
The cheapest place to lose a gate is in rehearsal. Attack the PM's deck the way the real audience will â armed with the registry, which knows exactly where the evidence is thin.
In real corporate work the most valuable data arrives through the side door â someone else's deck, an ad-hoc export, a wiki page. This job turns such an artifact into typed evidence in the registry instead of a manual retyping exercise.
Navigation layer: jobs map + registry rules here, per-step details in `references/steps.md` (read only the section you are executing).
Discovery without this step never learns: hypotheses get "confirmed" by analytics, solutions ship, and nobody checks whether the metric actually moved. This job is the difference between a pipeline and a feedback system.
The structuring engine of `/hypotheses` (step 1) and the synthesis logic of `/validate` (step 6). For a facilitated partner-led thinking session on a problem that is not an initiative yet, use `/deep-think`.
Generates the strategic story connecting your roadmap to company goals in a form non-technical stakeholders can repeat. Also structures Gate presentation narratives with source-backed claims. Use when user needs to "explain the roadmap", "present strategy to leadership", "create a narrative for all-hands", "build Problem Research Report", "build Solution Research Report", or "make the roadmap tell a story".
Boundary: **this skill = what the system looks like and what constrains the initiative** (feasibility input, PRD §9â10). What will be built for this initiative belongs to `technical-spec-document`.
One skill for both directions of the same loop: **what to instrument** (so hypotheses become measurable) and **how to read the funnel** (so measurements become verdicts). Serves `/brief` (steps 4â5), `/validate` (step 6) and experiment-design (step 14/16).
Serves the `/sketch` job: turn a solution hypothesis into concrete screens. The question is never "which component is prettiest" â it's **"which pattern delivers the mechanism this hypothesis promises"**.
You are an expert in agile development methodologies, user story creation, and requirements engineering. You excel at transforming high-level requirements, features, or business needs into well-structured, actionable user stories that follow industry best practices and enable effective sprint planni
One skill, two depths. Pick by what's at stake:
Auto-indexed from lenar-amirov/product-pipeline-public
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.