ask-questions-embedded-stm32-freertos

Identify and lock down ambiguities in embedded STM32 + FreeRTOS tasks before implementation.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/AntonBespalov/WC_IST --skill ask-questions-embedded-stm32-freertos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask-questions-embedded-stm32-freertos
Source: https://github.com/AntonBespalov/WC_IST/tree/main/.codex/skills/ask-questions-embedded-stm32-freertos
Command: npx skills add https://github.com/AntonBespalov/WC_IST --skill ask-questions-embedded-stm32-freertos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambiguities in embedded STM32 + FreeRTOS task requirements often lead to misinterpretations and unsafe changes. This guide defines a minimal, mandatory question set to halt implementation until essential details are resolved.

Core Features & Use Cases

  • Defines a mandatory set of clarifying questions (0–7) to gate development.
  • Provides recommended defaults to accelerate safe starts and reduce decision fatigue.
  • Use Case: apply during task briefing, design review, or code initiation to lock down acceptance criteria and safety constraints before coding.

Quick Start

Answer the mandatory questions (0–7) or approve defaults to proceed with safe development.

Frequently Asked Questions about ask-questions-embedded-stm32-freertos

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

FAQPage Schema
How do I clarify ambiguous STM32 FreeRTOS task requirements before coding?

To clarify ambiguous STM32 FreeRTOS task requirements, apply a mandatory set of questions and defined assumptions to gate development progress. This approach locks down acceptance criteria and safety constraints before implementation begins.

What are the essential safety guards for embedded FreeRTOS design reviews?

Essential safety guards for embedded FreeRTOS design reviews involve enforcing mandatory clarifying questions and defining acceptance criteria. This gatekeeping process halts implementation until critical safety constraints are fully resolved.

How do I prevent unsafe changes when implementing STM32 FreeRTOS tasks?

Preventing unsafe changes during STM32 FreeRTOS task implementation requires gating progress with a mandatory question set. Resolving ambiguities in task briefs and establishing safe defaults beforehand reduces misinterpretations.

What is the best way to lock down embedded task acceptance criteria during design?

Locking down embedded task acceptance criteria during design is best achieved by enforcing mandatory clarifying questions. This gatekeeping step ensures all ambiguities are resolved and safety guards are defined before code initiation.

Do I need to answer all mandatory questions to proceed with embedded development?

You do not need to manually answer all mandatory questions to proceed with embedded development. You can approve recommended defaults to accelerate safe starts and reduce decision fatigue while maintaining safety guards.

When should I apply gatekeeping questions for STM32 and FreeRTOS projects?

Apply gatekeeping questions for STM32 and FreeRTOS projects during task briefings, design reviews, or code initiation. This ensures requirements are fully clarified and ambiguities are locked down before any implementation starts.