Skf brief skill

Skill armelhbobdad/oh-my-skills/.claude/skills/skf-brief-skill

Curated collection of agentskills.io-compliant, version-pinned agent skills — generated and maintained by Skill Forge

Install

npx -y skills add armelhbobdad/oh-my-skills --skill skf-brief-skill

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Design a skill scope through guided discovery. Use when the user requests to "create a skill brief" or "brief a skill."

SKILL.md

2.6 KB, 612 tokens by cl100k_base, as published. Nobody here has run it

Brief Skill

Overview

Helps the user define what to skill — target repo, scope, language, inclusion/exclusion patterns — and produces a skill-brief.yaml that drives create-skill. This is the first step in the skill creation pipeline. The brief becomes the input contract for create-skill, which performs the actual compilation.

Role

You are a skill scoping architect collaborating with a developer who wants to create an agent skill. You bring expertise in source code analysis, API surface identification, and skill boundary design, while the user brings their domain knowledge and specific use case. Work together as equals.

Workflow Rules

These rules apply to every step in this workflow:

Read each step file completely before taking any action
Follow the mandatory sequence in each step exactly — do not skip, reorder, or optimize
Only load one step file at a time — never preload future steps
Always communicate in {communication_language}
If {headless_mode} is true, auto-proceed through confirmation gates with their default action and log each auto-decision

Stages

#	Step	File	Auto-proceed
1	Gather Intent	steps-c/step-01-gather-intent.md	No (interactive)
2	Analyze Target	steps-c/step-02-analyze-target.md	Yes
3	Scope Definition	steps-c/step-03-scope-definition.md	No (interactive)
4	Confirm Brief	steps-c/step-04-confirm-brief.md	No (confirm)
5	Write Brief	steps-c/step-05-write-brief.md	Yes
6	Workflow Health Check	steps-c/step-06-health-check.md	Yes

Invocation Contract

Aspect	Detail
Inputs	target_repo [required], skill_name [required], scope_hint [optional], language_hint [optional]
Gates	step-01: Input Gate [use args]
Outputs	skill-brief.yaml
Headless	All gates auto-resolve with default action when `{headless_mode}` is true

On Activation

Load config from {project-root}/_bmad/skf/config.yaml and resolve:
- project_name, output_folder, user_name, communication_language, forge_data_folder, sidecar_path
Resolve {headless_mode}: true if --headless or -H was passed as an argument, or if headless_mode: true in preferences.yaml. Default: false.
Load, read the full file, and then execute ./steps-c/step-01-gather-intent.md to begin the workflow.

What ships with it: 8 files

58.4 KB alongside SKILL.md

assets/

scope-templates.md6.5 KB
skill-brief-schema.md17.6 KB

steps-c/

Gives 0 of the 12 instructions most plan spec skills give in 612 tokens

Counted across 1,099 of the 1,860 authors here whose files we hold, read 2026-08-07

Ask one question at a timein 51 of 1099
Break plans into vertical slicesin 29 of 1099, across 11 files
Publish issues in dependency orderin 27 of 1099, across 9 files
Iterate until user approves the breakdownin 25 of 1099, across 7 files
Explore the repository to understand the codebase statein 24 of 1099, across 7 files
Use domain glossary vocabularyin 23 of 1099, across 5 files
Apply correct triage labels to published issuesin 23 of 1099, across 5 files
Prefer AFK slices over HITLin 22 of 1099, across 7 files
Write a specification before writing any codein 22 of 1099, across 14 files
Write failing tests before implementation codein 22 of 1099, across 20 files
Ask clarifying questions until requirements are concretein 21 of 1099, across 13 files
Respect existing architecture decision recordsin 20 of 1099, across 5 files

Said here and by no other author read

load only one step file at a time
communicate in the specified language
Follow the mandatory sequence exactly
Auto-proceed gates if headless mode is true
Load config from the project root on activation
Resolve headless mode from arguments or preferences

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.