night

Automate end-to-end feature delivery from planning to PR merge.

181|29|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/iusztinpaul/squid --skill night
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: night
Source: https://github.com/iusztinpaul/squid/tree/main/skills/night
Command: npx skills add https://github.com/iusztinpaul/squid --skill night

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a deterministic, end-to-end feature pipeline using a five-agent architecture to convert a feature spec into a pull request, with gating and audits.

Core Features & Use Cases

  • End-to-end feature delivery from planning to merge via PM, SWE, Tester, On-Call, and PR Reviewer.
  • Per-task implementation, verification, and per-task commits on a feature branch.
  • Multi-stage governance with two human gates and optional self-improve pass.

Quick Start

Provide a feature specification to start the nightly end-to-end pipeline.

Frequently Asked Questions about night

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

FAQPage Schema
How do I automate end-to-end feature delivery from planning to pull request merge?

Automating end-to-end feature delivery is handled by a five-agent pipeline that processes a feature specification from plan grooming through PM gating, SWE implementation, testing, and PR merge. It enforces per-task commits and multi-stage approvals to ensure reproducible, auditable outcomes.

What is a deterministic feature delivery pipeline and when do I need one?

A deterministic feature delivery pipeline is an orchestrated process that converts a feature spec into a PR using defined stages like PM gating and testing. You need this when you require reproducible, auditable outcomes with task-level governance, multi-stage approvals, and per-task commits on a feature branch.

How do I enforce task-level governance and per-task commits on a feature branch?

To enforce task-level governance and per-task commits, the feature delivery pipeline must implement per-task implementation and verification steps. This ensures each task within the feature branch is committed individually, coupled with frontmatter metadata enforcement and multi-stage approvals for auditable results.

Can I include human gating and optional self-improvement in an automated QA orchestration pipeline?

Including human gating and optional self-improvement in an automated QA orchestration pipeline is supported through multi-stage governance. The pipeline features two human gates and an optional self-improve pass within its five-agent architecture to ensure deterministic, auditable feature delivery.

Does this feature delivery pipeline require dependencies to run single-feature runs?

Running single-feature runs from plan grooming to PR merge does not require external dependencies. The pipeline operates autonomously using its internal five-agent architecture to handle implementation, testing, rollout, and multi-stage approvals without prerequisite packages.