architect

Generate a validated software feature blueprint from project context.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/nazrulsoftwaredev/NIT_CRM_2 --skill architect-nazrulsoftwaredev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/nazrulsoftwaredev/NIT_CRM_2/tree/main/.agents/skills/architect
Command: npx skills add https://github.com/nazrulsoftwaredev/NIT_CRM_2 --skill architect-nazrulsoftwaredev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents costly development rework by forcing a structured, senior-engineer-led planning phase that aligns technical vocabulary and architectural decisions before a single line of code is written.

Core Features & Use Cases

  • Language Alignment: Identifies and defines ambiguous project terminology to ensure developer and AI are perfectly synced.
  • Decision Surfacing: Prioritizes high-impact architectural choices, providing expert-level recommendations for user validation.
  • Blueprint Generation: Produces a structured implementation plan including definitions, decisions, assumptions, and a step-by-step build guide.
  • Use Case: Use this before starting a complex feature to ensure your implementation strategy is sound and that you have accounted for edge cases that would otherwise cause bugs later.

Quick Start

Invoke the architect skill to review the proposed feature requirements and establish a technical implementation plan.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I create a technical blueprint for a complex software feature?

To create a technical blueprint, you must provide a clear feature description and existing project context. The planning process identifies ambiguous terminology, surfaces critical architectural decisions, and generates a validated step-by-step development roadmap.

Why does my software development strategy fail due to misaligned terminology?

Software development strategy fails when ambiguous project terminology causes misalignment between developers and AI agents. Structured technical planning defines this vocabulary upfront to prevent costly implementation rework and ensure robust feature execution.

What is the best way to align architectural decisions before writing code?

The best way to align architectural decisions is to run a senior-engineer-led planning phase that prioritizes high-impact choices. This approach provides expert-level recommendations for user validation before generating a structured implementation plan.

When do I need structured technical planning for my development roadmap?

You need structured technical planning before starting a complex software feature to ensure your implementation strategy is sound. This process surfaces critical architectural decisions and accounts for edge cases that would otherwise cause bugs later.

Can I use this architecture planning process for existing software projects?

Yes, you can use this architecture planning process for existing software projects by providing the current project context alongside the proposed feature description. It reviews the requirements to establish an actionable development roadmap.

What are the limitations of relying on an AI agent for software architecture planning?

The limitation of using an AI agent for software architecture planning is that it requires a clear feature description and existing project context to function. Without this validated input, it cannot accurately surface critical implementation decisions or generate a reliable blueprint.