skills.rest
Refinex-Space
Refinex-SpaceCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

harness-feat

Coordinate feature delivery and lifecycle governance in the Harness Powers control plane.

Updated Aug 23, 2026
Search Tags:#planning#verification#refactor#feature-delivery#execution-plan#control-plane
One-click install
npx skills add https://github.com/Refinex-Space/Refinex-Skills --skill harness-feat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-feat
Source: https://github.com/Refinex-Space/Refinex-Skills/tree/main/plugins/harness-powers/skills/harness-feat
Command: npx skills add https://github.com/Refinex-Space/Refinex-Skills --skill harness-feat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill centralizes feature lifecycle governance inside the Harness Powers control plane, aligning preflight checks, sprint contracts, active execution plans, incremental implementation, and verification into a single, auditable workflow.

Core Features & Use Cases

  • Preflight and contract alignment: ensures requirements, assumptions, and acceptance criteria are established before work begins.
  • Execution plan ownership: creates and maintains step-by-step execution plans under docs/exec-plans, guiding incremental implementation.
  • Verification and handoff: enforces evidence-backed verification and archiving for clean handoffs through harness-verify.

Quick Start

Announce at the start: enter harness-feat to begin feature lifecycle work and follow the required preflight, sprint contract, and execution plan steps.

Frequently Asked Questions about harness-feat

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

FAQPage Schema
How do I manage feature delivery with execution plans and preflight checks?▼

Feature delivery management uses preflight checks and execution plans to align sprint contracts and incremental implementation. It ties step-by-step plans to evidence, ensuring verification before handoff and archiving completed work.

What is the best way to enforce lifecycle governance for repository refactoring?▼

Lifecycle governance for repository refactoring enforces disciplined workflows by establishing preflight requirements and acceptance criteria before work begins. It maintains active execution plans and archives completed changes for clean handoffs.

How does incremental implementation verification work before code handoff?▼

Incremental implementation verification enforces evidence-backed checks before handoff through harness-verify. It requires tying step-by-step execution plans and validation evidence to each implementation step, enabling clean workflow archiving.

Do I need sprint contracts to start feature delivery in my control plane?▼

Sprint contracts are required to start feature delivery in the control plane. Preflight and contract alignment ensures requirements, assumptions, and acceptance criteria are established before execution plans and implementation work begins.

Can I coordinate significant refactors using active execution plans and preflight checks?▼

Significant refactors are coordinated using active execution plans and preflight checks within the control plane. This workflow creates step-by-step guidance under docs/exec-plans, enforcing incremental implementation and verification before handoff.

When should I not use a control plane workflow for feature delivery?▼

Control plane feature delivery workflows are unnecessary for minor changes lacking preflight requirements. It applies specifically to new features, significant refactors, and repository changes requiring sprint contracts, execution plans, and verification.

Related Skills

Explore More Software Engineering Skills→
tomguntomgun

planning-features

Create implementation plans for software features with scope, files, acceptance criteria, and risks.

Community
Intermediate
ruan-catruan-cat
4

openspec-archive-change

Archive completed changes into dated folders under openspec/changes/archive.

Community
Intermediate
OzeroHAXOzeroHAX
32

docs-dev-plan

Document step-by-step implementation plans with dependencies, risks, and checkpoints.

Community
Basic
eng-vmessiaheng-vmessiah
2

pd

Enforce gated transitions between specification, planning, implementation, and verification phases.

Community
Advanced