accept-feature
- Repo stars 12
- Author updated Live
- Author repo temple8
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @nullhack · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: accept-feature
description: Validate business behavior against BDD examples from the end user's perspective Available knowle…
category: other
runtime: no special runtime
---
# accept-feature output preview
## PART A: Task fit
- Use case: Validate business behavior against BDD examples from the end user's perspective Available knowledge: [[requirements/gherkin#key-takeaways]], [[software-craft/test-design#key-takeaways]], [[software-craft/test-stubs#concepts]]. in artifacts: read all before starting work. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Decide Fit First / Design Intent / How To Use It” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Validate business behavior against BDD examples from the end user's perspective Available knowledge: [[requirements/gherkin#key-takeaways]], [[software-craft/test-design#key-takeaways]], [[software-craft/test-stubs#concepts]]. in artifacts: read all before starting work. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Decide Fit First / Design Intent / How To Use It” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Decide Fit First / Design Intent / How To Use It”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: accept-feature
description: Validate business behavior against BDD examples from the end user's perspective Available knowle…
category: other
source: nullhack/temple8
---
# accept-feature
## When to use
- Validate business behavior against BDD examples from the end user's perspective Available knowledge: [[requirements/gh…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Decide Fit First / Design Intent / How To Use It” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "accept-feature" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Decide Fit First / Design Intent / How To Use It
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Accept Feature
Available knowledge: [[requirements/gherkin#key-takeaways]], [[software-craft/test-design#key-takeaways]], [[software-craft/test-stubs#concepts]]. in artifacts: read all before starting work.
- Run
task test-buildto verify all tests pass with coverage. - Verify all BDD examples pass from the end user's perspective, not the test harness, per [[software-craft/test-design#key-takeaways]].
- IF an example passes in the test harness but fails from the user's perspective → flag it as a semantic alignment gap per [[software-craft/test-design#concepts]].
- Verify structural traceability: run
beehave status --jsonfor stage overview, thenbeehave checkfor detailed violations per [[software-craft/test-stubs#concepts]]. Every Example in the feature file must have exactly one corresponding test function, and every test function must trace back to an Example. The feature stage must beokandbeehave checkmust produce no output. - Verify semantic depth per [[software-craft/test-design#concepts]].
- Verify quality attributes are met.
- Verify definition of done criteria are satisfied.
- Produce a traceability matrix: for each stakeholder Q&A topic from interview notes, map to:
- Behavioral Q&A: a passing test (Example title → test function name).
- Technology Q&A: implementation evidence (import, module structure, config) where the technology named in the Q&A is exercised in code. Technology Q&As are verified by reading the feature file's
# Constraints:and checking the corresponding implementation — NOT through behavioral tests. - Explicit stakeholder deferral: with the reason it was deferred. Untraced Q&As of either type → incomplete delivery.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review