skills.rest
ohnotnow
ohnotnowCOMMUNITY
Explore all skills by this author →
GitHub

feature-workflow

Orchestrate end-to-end feature development with ait issue tracking.

1|Updated Feb 22, 2026
Search Tags:#workflow#planning#feature#issue-tracking#plan-mode#ait
One-click install
npx skills add https://github.com/ohnotnow/agentic-stuff --skill feature-workflow-ohnotnow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-workflow
Source: https://github.com/ohnotnow/agentic-stuff/tree/main/skills/feature-workflow
Command: npx skills add https://github.com/ohnotnow/agentic-stuff --skill feature-workflow-ohnotnow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating end-to-end feature work across teams can be manual, fragmented, and slow. This Skill provides a repeatable, plan-driven workflow powered by ait issue tracking to align discovery, planning, and implementation.

Core Features & Use Cases

  • Phase-based guidance (Orient, Explore & Plan, Implement, Iterate, Wrap Up) to move ideas from concept to done.
  • Plan-mode enforcement that requires exploration and planning before changes are made.
  • Automatic creation and tracking of ait issues from plan steps with explicit acceptance criteria and status updates.

Quick Start

Start by outlining your feature and begin Phase 1 to orient the project context.

Frequently Asked Questions about feature-workflow

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

FAQPage Schema
How do I coordinate end-to-end feature planning and implementation across multiple sessions?▼

End-to-end feature planning is coordinated through a phase-based workflow that enforces plan mode, guiding discovery and implementation while automatically tracking issues to keep multi-session work aligned.

What is the best way to automate issue tracking from a development plan?▼

Automating issue tracking from a development plan is achieved by converting plan steps into tracked issues, establishing explicit acceptance criteria, and updating statuses iteratively as implementation progresses.

Does this feature workflow require exploration before implementation begins?▼

Yes, plan mode is strictly enforced to ensure thorough exploration and planning phases are completed before any code changes are allowed, preventing premature implementation.

How do I verify acceptance criteria during iterative feature development?▼

Acceptance criteria are verified during an iterative wrap-up phase that checks established conditions, refines implementation based on feedback, and updates tracked issue statuses accordingly.

Can I use this workflow for new features across different codebases and teams?▼

This workflow supports applying new feature development across various codebases and teams by providing a repeatable, plan-driven structure that standardizes discovery, planning, and implementation.

Related Skills

Explore More Product & Management Skills→
hilaryosbornehilaryosborne

qa-planning

Define quality assurance strategies and outline comprehensive test plans for software projects.

Community
Basic
mckissingermckissinger
1

verify-milestone

Verifies completed software milestones against specifications and acceptance criteria before code acceptance.

Community
Advanced
warpdotdevwarpdotdev
292

implement-specs

Plan and execute feature implementations while keeping specs aligned with code changes.

Official
Advanced
mfittkomfittko
14

dev-loop

Automate GitHub issue-to-merged PR workflows through seven deterministic phases.

Community
Advanced