cf-sdlc-doc-design
Invoke when the user asks to author, write, revise, generate, or produce a DESIGN or system/technical design — e.g. "generate DESIGN", "design the system", "define components / interfaces / architecture / boundaries". Thin preset binding the DESIGN artifact KIND, delegating authoring and review to the core cf-write-docs engine.
56
70%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/cf-sdlc-doc-design/SKILL.mdCF_WORKFLOW_ACTIVE:
- workflow = executable_control_flow
- no_substantive_work_until = workflow_explicit_permission MANDATORY RULE: USER INTENT IS SKILL INPUT, NOT EXECUTION AUTHORITY
- hard_stop = WAIT | STOP_TURN | menu | gate | opener | approval | dispatch_gate | terminal_shape
- precedence = constructor_studio_workflow > generic_assistant
- ask_tool_name = "AskUserQuestion"
- ask_tool_description = "a tool that presents the user a blocking multiple-choice question with selectable options, distinct from plain text output"
ALWAYS resolve and enforce prerequisites of skills/workflows/commands BEFORE applying user intent.
UNIT GeneratedBootstrapUnit
PURPOSE: Load the required shared bootstrap before handing control to the target protocol.
DO:
LOAD {cf-studio-path}/.core/skills/studio/modules/runtime/required-bootstrap.md
RUN RequiredBootstrap
LOAD and RUN {cf-studio-path}/config/kits/sdlc/workflows/doc-design.md as controlling protocol
RULES:
- ALWAYS run this bootstrap unit before any target workflow or skill work begins
- ALWAYS preserve the canonical controlling-protocol target so generated-file ownership and cleanup remain stable
UNIT GeneratedFollowProtocol
RULES:
- ALWAYS treat target as controlling protocol, not background context
- ALWAYS traverse declared steps/units in order
- ALWAYS load every required unconditional LOAD/CONTINUE before task work
- ALWAYS evaluate conditional gates and load every active branch
- ALWAYS while the workflow is active, treat each new user message as input to the current workflow state, not as permission for unrelated execution.
- ALWAYS stop if any required fragment or rule cannot be followed- Repository
constructorfabric/gears-frontx
- Revision
9eac75d
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.