Menu
Create a new feature file for ATDD workflow - must be done BEFORE any implementation
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/bdfinst/vsm-workshop --skill new-featureThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Implement an approved feature file using ATDD workflow with test-first development
Analyze code with Semgrep for security vulnerabilities and code quality issues, then create a prioritized fix plan
Add a new calculated metric to the VSM dashboard with test-first development
Based on SOC occupation classification
Showing SKILL.md
| name | new-feature |
| description | Create a new feature file for ATDD workflow - must be done BEFORE any implementation |
| user-invocable | true |
| allowed-tools | Read, Write, Edit, Grep, Glob |
Create a new feature file for ATDD workflow. This must be done BEFORE any implementation.
/new-feature <FeatureName>
features/{category}/{feature-name}.featureFeature: {Feature Name}
As a {role}
I want {capability}
So that {benefit}
Background:
Given {common preconditions}
Scenario: {Primary happy path}
Given {initial context}
When {action taken}
Then {expected outcome}
Scenario: {Alternative path or edge case}
Given {initial context}
When {different action}
Then {different outcome}
Scenario Outline: {Parameterized scenario}
Given {context with <parameter>}
When {action with <input>}
Then {outcome with <expected>}
Examples:
| parameter | input | expected |
| value1 | in1 | out1 |
| value2 | in2 | out2 |
When writing features for Norn, consider these common patterns:
Scenario: Add a process step to the value stream
Given I have an empty value stream map
When I add a step named "Development" with process time 60 minutes
Then the map should contain 1 step
And the step should display "Development"
Scenario: Calculate flow efficiency
Given a value stream with total process time of 120 minutes
And total lead time of 480 minutes
When I view the metrics dashboard
Then the flow efficiency should show "25%"
Scenario: Simulate work flowing through the stream
Given a value stream with 3 steps
And 10 work items in the queue
When I run the simulation for 100 ticks
Then I should see work items moving through each step
Before presenting for review, verify: