Session init
Auto-loaded at session start. Resumes active pipelines, routes tasks to stn-skills. Triggers: session start, /stn-skills:session-init.From its SKILL.md
npx -y skills add sthiermann/stn-skills --skill session-initAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 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.
SKILL.md
2.9 KB, as published. Nobody here has run it
Subagent Guard
If you were dispatched as a subagent to execute a specific task, skip this skill entirely. Only the top-level orchestrator routes.
Instruction Priority
- User project rules (CLAUDE.md, direct instructions) — highest priority
- stn-skills — override default behavior where they apply
- Default system prompt — lowest priority
If CLAUDE.md contradicts a skill instruction, follow CLAUDE.md. The user is in control.
Pipeline State
ACTIVE PIPELINES ARE RESUMED FIRST.
THE STATE FILE IS THE TRUTH.
Plan Mode Override
If plan mode is active and a skill matches the user's intent, invoke it — the skill itself handles exploration, planning, and execution with proper structure.
Active Pipeline
If an Active Pipeline State section appears below, a pipeline is active.
- Report status to user.
- Invoke the listed skill via Skill tool immediately.
- Do NOT start other work until user acknowledges the pipeline.
No Active Pipeline State section? Use routing below.
Routing
Match by INTENT, not literal keywords. The user may write in any language. Classify what the user wants to accomplish, then match to the closest skill.
| Priority | Intent | Skill |
|---|---|---|
| 1 | Active pipeline state | Resume stn-skills:{active_skill} |
| 2 | Build, create, implement, or deliver a feature or significant change — any task touching multiple files that benefits from design-before-code | stn-skills:build-feature |
| 3 | Explore options, compare approaches, make an architectural or design decision | stn-skills:brainstorming |
| 4 | Decompose requirements into tasks, create an implementation plan | stn-skills:plan-writing |
| 5 | Execute an existing plan step by step | stn-skills:plan-execution |
| 6 | Audit, review, or assess repository health, security, or quality | stn-skills:codebase-audit |
| 7 | Set up or update project quality standards, generate CLAUDE.md | stn-skills:codebase-quality-bootstrap |
Multiple match? Use higher priority.
No match? Proceed without a skill. Only use skills when they genuinely add value.
Skip
Do NOT invoke when: simple question, single-file fix, no code changes, user says "skip".
Pipeline
brainstorming -> plan-writing -> plan-execution. Each outputs an artifact for the next. build-feature orchestrates all three. codebase-audit can initiate a pipeline when findings require design or multi-file remediation — it writes the pipeline state and hands off to brainstorming or plan-writing. State: .claude/stn-skills-pipeline-state.json.
When NOT to Route
- Simple questions, single-file fixes, no code changes
- User says "skip"
- Task clearly doesn't benefit from structured pipeline