feature

Solid

Add a feature to an existing project with a full sprint. Skips /think diagnostic, goes straight to planning. Use when the user knows what they want and the project already exists. Triggers on /feature.

Code & Development 1 stars 0 forks Updated yesterday Apache-2.0

Install

View on GitHub

Quality Score: 80/100

Stars 20%
10
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# /feature — Add a Feature Fast path for adding a feature to an existing project. Skips the /think diagnostic and runs the full sprint via skill invocations. ``` /feature Add import from JSON/CSV to restore backups ``` ## Setup Before anything else, ensure the project is configured. Run this once (skips if already done): ```bash [ -f .claude/settings.json ] || ~/.claude/skills/nanostack/bin/init-project.sh ``` ## Session Initialize the sprint session: ```bash ~/.claude/skills/nanostack/bin/session.sh init feature ``` Then run `session.sh phase-start plan`. This activates the phase gate — `git commit` will be blocked until review, security, and qa are complete. ## Process You are an autonomous orchestrator. You run the entire sprint without stopping between phases. Do NOT wait for user input between steps. Do NOT ask "should I continue?" or "ready for review?". Invoke each skill, wait for it to complete, then immediately invoke the next one. The only reasons to stop are blocking issues or critical vulnerabilities. ### Step 1: Context Resolve existing artifacts and solutions in one call: ```bash ~/.claude/skills/nanostack/bin/resolve.sh feature ``` The output is JSON with `upstream_artifacts` (think, plan, ship paths if recent) and `solutions` (ranked past learnings). Read the checkpoint summaries. If no artifacts exist, read the codebase directly. ### Step 2: Plan ``` Use Skill tool: skill="nano" ``` Wait for /nano to complete. It saves its own artifact. Then...

Details

Author
Jihadyip286
Repository
Jihadyip286/nanostack
Created
3 months ago
Last Updated
yesterday
Language
Shell
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

new-feature

Start a new feature with full planning. Use PROACTIVELY, without being asked by name, whenever the user asks to start any new feature or substantial piece of work — 'build X', 'add X feature', 'implement X', 'create X', 'let's start working on X', 'new feature' — anything beyond a trivial one-file edit.

0 Updated today
YoniChechik
Code & Development Listed

feature

End-to-end feature workflow around the agent — spec by interview, a plan of 2–5-minute tasks, test-first execution with checkpoint commits, then an evidence-gated finish. Effort-scaled: a one-sentence diff skips straight to implementation; a real feature gets spec.md → plan.md → task-by-task TDD, with all state in out/dev/<change>/ so any later session resumes at the first unchecked task. Human-in-the-loop: the spec and the plan are approved (and editable) before any code is written, and nothing ships without the done gate. Use when the user wants to build, add, or implement a feature or start non-trivial coding work — e.g. "/feature add rate limiting", "implement X", "build a Y that Z", "resume the <change> feature". For fixing something broken use bugfix; for just the end-of-session shipping gate use done; for this whole loop end-to-end without approval stops, suggest the user run /autopilot (explicit invocation only).

7 Updated yesterday
duthaho
AI & Automation Solid

plan-feature-scaffold

Internal step of plan-feature: from an already-designed SPEC (product half `designed`), fill the **engineering half** and generate the planning artifact set scaled to the feature's size (XS/S → SPEC-only with ≥ 2 phases in the SPEC, last = Hardening & PR; M/L → full set with a hardening phase) and register the roadmap entry. Docs only — never code.

19 Updated 1 weeks ago
gtrabanco