design-technical-solution
openbooklet.com/s/design-technical-solutionopenbooklet.com/s/design-technical-solution@1.0.0GET /api/v1/skills/design-technical-solutionSelect technology stack, document dependencies, and route architecturally significant decisions to ADRs
Validate business behavior against BDD scenarios from the end user's perspective
Evaluate whether the feature requires new architecture or fits the existing system, verify delivery mechanism
Commit the reviewed, passing implementation with traceability to feature files
Interview stakeholders to elicit pain points, business goals, domain terms, and quality attributes
Create minimum typed stubs and test stubs as domain model breadcrumbs for the current feature, then verify all planning artifacts are complete for baseline
Ask the stakeholder whether to publish the accumulated batch as a PR or continue accumulating features on local main
Define what the product IS and IS NOT, who the users are, and the delivery order
Extract domain terms from the domain model and interview notes, define them in genus-differentia format, and cross-reference against domain model and features
Create logo and banner using favicon-first, monochrome-first, progressive-simplification process
Select and validate a colour palette with WCAG contrast, dark-mode counterparts, and hue semantics
Determine whether the feature needs replanning, architecture changes, or should be abandoned
Identify feature boundaries from the delivery order, validated against bounded contexts and aggregate boundaries
Derive business rules and constraints from domain model artifacts (events, invariants, commands) and map them to feature files
Convergent synthesis: formalize event storming candidates into bounded contexts, entities, relationships, aggregate boundaries, and context map
Determine the corrective fix and update the post-mortem with remediation steps
Map bounded context relationships, Vernon patterns, and anti-corruption layers into domain_model.md
Squash-merge feature commits into local main, pull remote main, and resolve conflicts
Select the next feature to develop by detecting delivery status from disk evidence, following delivery order
Apply text substitutions, rename package directory, and write templates
Interview stakeholder to establish brand identity: personality, visual metaphor, wording, and release naming
Auto-indexed from nullhack/temple8
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.