# Architect Propose

> 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.

- **Type:** Skill
- **Install:** `agentstack add skill-hlhr202-swe-skills-architect-propose`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [hlhr202](https://agentstack.voostack.com/s/hlhr202)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [hlhr202](https://github.com/hlhr202)
- **Source:** https://github.com/hlhr202/swe-skills/tree/main/skills/architect-propose

## Install

```sh
agentstack add skill-hlhr202-swe-skills-architect-propose
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Architect Propose

Use this skill to create a new Architect track for an already initialized Architect project. A track is a focused unit of work, such as a feature, bug fix, chore, refactor, or setup milestone.

## Core Rules

- Follow the bundled resource `references/propose-track-protocol.md` as the source of truth.
- Use Architect semantics consistently: `architect/`, `/architect-*`, `Architect methodology`, and `architect(...)` commit scopes.
- Require an initialized Architect context before creating a track.
- Use relative paths rooted in the user's project when creating Architect files. Architect-managed files must stay under `architect/`; do not use absolute paths, `..`, or track links outside `architect/tracks/`.
- Ask the user through the active agent runtime's user-interaction mechanism. If structured choices are unavailable, present the options in text and wait for the user's reply.
- Present detailed Markdown, drafts, diffs, reports, or risk analysis in a normal assistant message before asking for a decision. Use interactive prompts only for concise plain-text questions and short plain-text choices.
- Use the active agent runtime's safest reviewable file-editing mechanism, preferably patch-based, for manual file creation and edits. Do not use shell redirection to write files.
- Validate each operation result before continuing. If a step fails, correct it once when the error is clear; otherwise stop and report the blocker.
- Do not commit unless the user explicitly asks for a commit in the current conversation.

## Execution

1. Read the bundled resource `references/propose-track-protocol.md`.
2. Verify required Architect context files exist.
3. Gather or use the track description.
4. Generate and confirm `spec.md`.
5. Generate and confirm `plan.md` from `architect/workflow.md`.
6. Create the track directory and artifacts.
7. Update `architect/tracks.md`.
8. Summarize created files and next steps.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [hlhr202](https://github.com/hlhr202)
- **Source:** [hlhr202/swe-skills](https://github.com/hlhr202/swe-skills)
- **License:** Apache-2.0

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-hlhr202-swe-skills-architect-propose
- Seller: https://agentstack.voostack.com/s/hlhr202
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.
