Skip to content
Back to skills

New Feature

ASecurity

Clear the scratch directory and start a fresh feature context. Load when starting a new feature or resetting pipeline state.

  • 15 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 20, 2026
ai-agentspythonbashgit

Security analysis

A93/100
  • highPerforms destructive filesystem operations

Pro shows the line behind each finding and how to fix it

Scanned September 20, 2026

npx -y skills add woditschka/agentic-coding-reference --skill new-feature --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of New Feature?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for New Feature
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/woditschka-new-feature/badge)](https://www.skillsdirectory.com/skills/woditschka-new-feature)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: new-feature
description: >-
  Clear the scratch directory and start a fresh feature context.
  Load when starting a new feature or resetting pipeline state.
compatibility:
  - claude-code
  - github-copilot
  - opencode
metadata:
  version: "1.0"
  author: team
---

# New Feature

Clear the `.scratch/` directory and start a fresh feature context.

## Instructions

1. Guard the removal: when `.scratch/handoff.jsonl` exists, run `python3 scripts/handoff.py route` first — `no-active-slice` clears it; any other decision surfaces to the user before anything is wiped. A `blocked` `human-consultation` is a paused elicitation awaiting the human's answer, never stale state.
2. Remove the entire `.scratch/` directory.
3. Recreate `.scratch/tmp/`. The `handoff.jsonl` file is created on first append by the product-requirements-expert; do not pre-create it.
4. Report what was cleared and confirm the directory is ready.
5. When the request needs discussion, load the `intake` skill: the discussion runs in this session under the product expert's contract and exits by recording an `intake-decision` — the owner's request and decisions, quoted verbatim. `route` then dispatches `product-requirements-expert` on the record (`intake-ready`). When no reply can arrive, skip the discussion and seed the `intake-decision` from the request as stated (`source: "task-prompt"`). Never seed while a `consultation-request` targeting `human` is pending — that pause resolves only through the human's reply. Invoke the `pipeline-coordinator` only for intake that neither the `intake` skill nor the `next` triage covers.

## Execution

```bash
rm -rf .scratch && mkdir -p .scratch/tmp
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…