architecting

Name: architecting
Availability: InStock
Author: vidyfoo

Architect features through DESIGN, EXTEND, and BUILD workflows with spec.md documents.

12|3|Updated Jan 11, 2026

Search Tags:#design #architecture #documentation #spec-generation #architecting #feature-lifecycle

Ready to run

npx skills add https://github.com/VidyFoo/antigravity-skill-engine --skill architecting

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecting
Source: https://github.com/VidyFoo/antigravity-skill-engine/tree/main/.agent/skills/1-dev/architecting
Command: npx skills add https://github.com/VidyFoo/antigravity-skill-engine --skill architecting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecting provides end-to-end architectural governance for features, ensuring consistency from design through deployment and UX integrity across teams.

Core Features & Use Cases

DESIGN mode: generate and validate feature specifications, architecture decisions, and dependencies.
EXTEND mode: evolve existing features with extension plans and implementation guidance.
BUILD mode: implement features following a layered, type-first approach with self-verification and alignment to the spec.

Quick Start

Create a new feature directory under src/features/{name} and generate a spec.md describing design, then implement according to the spec using the DESIGN/EXTEND/BUILD workflows.

Frequently Asked Questions about architecting

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

FAQPage Schema

What is feature lifecycle architecture and when do I need to document it?▼

Feature lifecycle architecture governs a feature from concept to deployment across teams. You need it to enforce a consistent DESIGN, EXTEND, and BUILD workflow, ensuring architectural decisions and UX integrity are documented in spec.md files.

How do I generate feature specifications and architecture decisions for a new feature?▼

Generate feature specifications by creating a feature directory under src/features/{name} and using DESIGN mode. This mode produces a spec.md document detailing architecture decisions, dependencies, and design validation for the new feature.

How do I plan implementation for extending an existing feature across teams?▼

Plan implementation for extending features by using EXTEND mode. It generates extension plans and implementation guidance, ensuring the evolved feature aligns with existing architecture and maintains UX integrity across teams.

Does this approach enforce a specific workflow for building and deploying features?▼

Yes, the approach enforces a DESIGN/EXTEND/BUILD workflow. BUILD mode implements features using a layered, type-first approach with self-verification, ensuring alignment with the generated spec.md before deployment.

What is the best way to maintain architectural consistency from design through deployment?▼

Maintain architectural consistency by applying end-to-end governance through the DESIGN/EXTEND/BUILD workflow. This provides guardrails for architecture decisions, generates spec.md documentation, and enforces self-verification during the build phase.

Can I use this for evolving existing features or is it only for new feature design?▼

You can use it for both. DESIGN mode handles new feature architecture and spec generation, while EXTEND mode specifically handles evolving existing features with targeted extension plans and implementation guidance.