faas

Plan and execute feature delivery through a four-phase Find, ARCH, Automate, and STR workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and execute feature delivery through a disciplined four-phase workflow: Find, ARCH, Automate, and STR.

Core Features & Use Cases

  • Four-phase workflow: Find, ARCH, Automate, STR, with exit gates at each phase.
  • Includes reference models such as 54321 layers and RDD patterns to guide design.
  • Supports interview-mode workflows for no-codebase contexts and structured discovery.

Quick Start

Describe your feature and run the four-phase workflow to plan, architect, automate, and test it end-to-end.

Frequently Asked Questions about faas

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

FAQPage Schema
What is a phase-driven workflow for feature delivery?

Feature delivery through a phase-driven workflow structures the process into four phases: Find, ARCH, Automate, and STR. Each phase enforces an exit gate to ensure structured discovery, architecture, test scaffolding, and handoff artifacts are completed before moving forward.

How do I plan and architect a feature when I don't have codebase access?

You can use an interview-mode workflow to plan and architect a feature without codebase access. This approach guides structured discovery through frontmatter-driven metadata and artifact templates to gather requirements and design architecture when direct code access is unavailable.

How do I structure test scaffolding and architecture for a new feature?

Structure test scaffolding and architecture by applying reference models like the 54321 layers and RDD patterns. These models guide the design phase to align test scaffolding with architectural decisions before generating final handoff artifacts.

Can I use phase-driven feature delivery for product team handoffs?

Yes, phase-driven feature delivery is applicable to product teams and engineers who want structured handoff artifacts. The workflow generates standardized artifacts like find.md, arch.md, automate.md, and STR files to ensure clear communication during team handoffs.

What are the limitations of the four-phase feature delivery workflow?

The four-phase workflow requires consistent frontmatter-driven SKILL.md metadata and strict adherence to exit gates at each phase. Users must also supply optional reference materials such as phases.md and rdd.md to fully guide architecture and test scaffolding.