feature

Orchestrate an end-to-end sprint to add a feature to an existing codebase.

204|14|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/garagon/nanostack --skill feature-garagon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/garagon/nanostack/tree/main/feature
Command: npx skills add https://github.com/garagon/nanostack --skill feature-garagon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq.

What problem does it solve?

Enables rapid delivery of a known feature by running a complete sprint (plan → build → review → security → qa → ship) automatically without pausing for user confirmations. It skips the diagnostic /think step and assumes the project already exists and the requester knows the desired outcome.

Core Features & Use Cases

  • End-to-end orchestration: Invokes Skill tools for planning, building, reviewing, security checks, QA, and shipping in one continuous flow.
  • Commit-time enforcement: Includes a PreToolUse hook that blocks git commits until plan, review, security, and qa artifacts are present and up-to-date for the current project.
  • Parallel validations: Runs review, security, and QA in parallel when possible, and re-runs only failing phases when blocking issues are found.
  • Use Case: Add a small incremental feature like import-from-CSV to restore backups and ship it in a single automated sprint.

Quick Start

Run /feature Add import from JSON/CSV to restore backups to execute a fast sprint that plans, builds, reviews, audits, and ships the feature.

Frequently Asked Questions about feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a full sprint to add a feature to an existing codebase?

Automated sprint orchestration runs plan, build, review, security, QA, and ship phases continuously. You provide the desired feature and existing project, and the flow executes end-to-end without pausing for manual confirmations.

Can I prevent git commits until code review, security, and QA artifacts pass?

Yes, commit-time enforcement blocks git commits until plan, review, security, and QA artifacts are present and current. A PreToolUse hook validates artifact presence before allowing any commit to proceed.

How do I run security and QA checks in parallel during an automated feature deployment?

Parallel validations execute review, security, and QA phases simultaneously when possible. If blocking issues are found, only the failing phases re-run automatically, ensuring fast feedback without redundant processing.

Do I need jq installed to orchestrate an end-to-end sprint for shipping code?

Yes, jq is a required dependency to run the end-to-end sprint orchestration. You must have this command-line JSON processor installed in your environment before initiating the automated workflow.

What is the best way to ship a small incremental feature like CSV import without manual intervention?

Running a fast automated sprint plans, builds, reviews, audits, and ships incremental features in one continuous flow. It skips diagnostic steps and assumes you already know the desired outcome and have an existing project.

When should I avoid using an automated sprint workflow for feature delivery?

Avoid automated sprint orchestration when the project does not exist yet or the desired feature is undefined. It skips diagnostic reasoning and requires a clear outcome and existing codebase to function correctly.