Run any Skill in Manus with one click

architect-discuss

Stars3

Forks0

UpdatedJuly 11, 2026 at 08:21

Use only when the user explicitly includes `architect-discuss` or directly asks to use the architect-discuss skill. Turns raw or ambiguous product and technical requirements into a product and architecture draft before tracked Architect proposal work.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

hlhr202

hlhr202/swe-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	architect-discuss
description	Use only when the user explicitly includes `architect-discuss` or directly asks to use the architect-discuss skill. Turns raw or ambiguous product and technical requirements into a product and architecture draft before tracked Architect proposal work.

Architect Discuss

Clarify early product and technical direction before tracked proposal work. Follow references/discuss-protocol.md as the source of truth.

Hard Boundaries

Require explicit architect-discuss invocation.
Do not create tracked Architect artifacts, modify implementation code, scaffold systems, or run implementation validation.
Save a standalone draft only to a user-confirmed safe relative path; never overwrite without exact confirmation.
Do not commit unless explicitly requested in the current conversation.

Run

Read references/discuss-protocol.md.
Qualify the trigger and build only the repository context needed for the discussion.
Progress through resumable gates; ask only material questions and auto-pass established decisions.
Generate the synthesis only after readiness, or explicitly label unresolved synthesis.
Offer continue, save, split, proposal handoff, or stop. Never execute the handoff automatically.

More from this repository

same repository

architect-implement

hlhr202/swe-skills

Implement or resume an existing Architect track by executing its approved plan and updating track status. Use when the user asks to implement, continue, resume, or complete a planned Architect track.

2026-07-163

architect-propose

hlhr202/swe-skills

Propose and create a new Architect track for an initialized project, including its spec, plan, metadata, and registry entry. Use when the user asks to add, plan, or propose a new feature, bug fix, chore, refactor, docs, or test track.

2026-07-113

architect-review

hlhr202/swe-skills

Review Architect track work or explicit current changes against project context, track intent, style guides, and tests. Use when the user asks to review, verify, audit, inspect, approve, or apply review fixes for Architect-managed work.

2026-07-113

architect-setup

hlhr202/swe-skills

Initialize or resume Architect project setup by creating only the core architect/ context. Use when the user asks to set up Architect, scaffold Architect context, or recover an interrupted setup before discussion or proposal work.

2026-07-113

architect-status

hlhr202/swe-skills

Report read-only Architect project status from core context and, when available, the tracks registry and plans. Use when the user asks for setup status, progress, current task, next action, blockers, completion percentage, or pending work.

2026-07-113

name	architect-discuss
description	Use only when the user explicitly includes `architect-discuss` or directly asks to use the architect-discuss skill. Turns raw or ambiguous product and technical requirements into a product and architecture draft before tracked Architect proposal work.

Architect Discuss

Clarify early product and technical direction before tracked proposal work. Follow references/discuss-protocol.md as the source of truth.

Hard Boundaries

Require explicit architect-discuss invocation.
Do not create tracked Architect artifacts, modify implementation code, scaffold systems, or run implementation validation.
Save a standalone draft only to a user-confirmed safe relative path; never overwrite without exact confirmation.
Do not commit unless explicitly requested in the current conversation.

Run

Read references/discuss-protocol.md.
Qualify the trigger and build only the repository context needed for the discussion.
Progress through resumable gates; ask only material questions and auto-pass established decisions.
Generate the synthesis only after readiness, or explicitly label unresolved synthesis.
Offer continue, save, split, proposal handoff, or stop. Never execute the handoff automatically.